Beam Failure Recovery

ABSTRACT

Systems, apparatuses, and methods are described for wireless communications. A wireless device may inform a base station of a failure of a beam failure recovery procedure for a secondary cell. The wireless device may include an indicator of the failure in a report providing, or configured to provide, values for signal strength or other characteristic of a downlink signal. The indicator may be in addition to, and/or may replace, one or more indicators of signal strength or other characteristic.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No.16/372,858, filed on Apr. 2, 2019, which claims the benefit of U.S.Provisional Application No. 62/651,419, filed on Apr. 2, 2018. Theabove-referenced applications are hereby incorporated by reference intheir entirety.

BACKGROUND

A wireless device may be configured to receive transmissions via one ofmultiple different beams associated with a cell. Although thiscapability can increase cell capacity, individual beams may be subjectto failure based on interruption (e.g., by passing vehicles or otherobjects), interference, transmission irregularities at a cell, etc. If abeam fails, action may be taken to recover the beam.

SUMMARY

The following summary presents a simplified summary of certain features.The summary is not an extensive overview and is not intended to identifykey or critical elements.

Systems, apparatuses, and methods are described for reporting a beamfailure recovery (BFR) procedure for a secondary cell. The BFR proceduremay have been unsuccessful and/or may have otherwise failed. A wirelessdevice may be unable to inform a base station of the BFR procedure for asecondary cell using the same procedure used for a primary cell. Awireless device may be configured to provide beam reporting for asecondary cell. That reporting, which may be sent via a physical uplinkcontrol channel (PUCCH) of the secondary cell and/or via a PUCCH ofanother cell, may include fields for indications of signal strengthand/or one or more other characteristics of downlink signals received bythe wireless device. The reporting may be modified to include anindication of a BFR procedure on the secondary cell. That indication ofthe BFR procedure may replace, in one or more of the fields, theindication of signal strength or other characteristic. The indication ofthe BFR procedure may be included in addition to indications of signalstrength and/or other characteristics.

These and other features and advantages are described in greater detailbelow.

BRIEF DESCRIPTION OF THE DRAWINGS

Some features are shown by way of example, and not by limitation, in theaccompanying drawings.

In the drawings, like numerals reference similar elements.

FIG. 1 shows an example radio access network (RAN) architecture.

FIG. 2A shows an example user plane protocol stack.

FIG. 2B shows an example control plane protocol stack.

FIG. 3 shows an example wireless device and two base stations.

FIG. 4A, FIG. 4B, FIG. 4C and FIG. 4D show examples of uplink anddownlink signal transmission.

FIG. 5A shows an example uplink channel mapping and example uplinkphysical signals.

FIG. 5B shows an example downlink channel mapping and example downlinkphysical signals.

FIG. 6 shows an example transmission time and/or reception time for acarrier.

FIG. 7A and FIG. 7B show example sets of orthogonal frequency divisionmultiplexing (OFDM) subcarriers.

FIG. 8 shows example OFDM radio resources.

FIG. 9A shows an example channel state information reference signal(CSI-RS) and/or synchronization signal (SS) block transmission in amulti-beam system.

FIG. 9B shows an example downlink beam management procedure.

FIG. 10 shows an example of configured bandwidth parts (BWPs).

FIG. 11A and FIG. 11B show examples of multi connectivity.

FIG. 12 shows an example of a random access procedure.

FIG. 13 shows example medium access control (MAC) entities.

FIG. 14 shows an example RAN architecture.

FIG. 15 shows example radio resource control (RRC) states.

FIG. 16A, FIG. 16B and FIG. 16C show examples of a MAC subheader.

FIG. 17A and FIG. 17B show examples of uplink/downlink (UL/DL) MACprotocol data unit (PDU).

FIG. 18A and FIG. 18B show examples of logical channel identifiers(LCIDs).

FIG. 19A and FIG. 19B show examples of secondary cell activation and/ordeactivation MAC control element (CE).

FIG. 20A and FIG. 20B show examples of a downlink beam failure.

FIG. 21 shows an example downlink beam failure recovery procedure.

FIG. 22 shows an example timeline for an example downlink beam failurerecovery procedure.

FIG. 23 shows an example downlink beam failure recovery procedure.

FIG. 24 is another example timeline for an example downlink beam failurerecovery procedure.

FIG. 25 shows a table of an example mapping of L1-RSRP values to 7-bitvalues.

FIG. 26A, FIG. 26B, FIG. 26C, and FIG. 26D show examples of reporting.

FIG. 27 shows example elements of a computing device that may be used toimplement any of the various devices described herein.

DETAILED DESCRIPTION

The accompanying drawings and descriptions provide examples. It is to beunderstood that the examples shown in the drawings and/or described arenon-exclusive and that there are other examples of how features shownand described may be practiced.

Examples are provided for operation of wireless communication systemswhich may be used in the technical field of multicarrier communicationsystems. More particularly, the technology described herein may, forexample, relate to failure recovery procedures and/or operationsassociated with failure recovery procedures.

The following acronyms are used throughout the drawings and/ordescriptions, and are provided below for convenience although otheracronyms may be introduced in the detailed description:

-   3GPP 3rd Generation Partnership Project-   5GC 5G Core Network-   ACK Acknowledgement-   AMF Access and Mobility Management Function-   ARQ Automatic Repeat Request-   AS Access Stratum-   ASIC Application-Specific Integrated Circuit-   BA Bandwidth Adaptation-   BCCH Broadcast Control Channel-   BCH Broadcast Channel-   BPSK Binary Phase Shift Keying-   BWP Bandwidth Part-   CA Carrier Aggregation-   CC Component Carrier-   CCCH Common Control CHannel-   CDMA Code Division Multiple Access-   CN Core Network-   CP Cyclic Prefix-   CP-OFDM Cyclic Prefix-Orthogonal Frequency Division Multiplex-   C-RNTI Cell-Radio Network Temporary Identifier-   CS Configured Scheduling-   CSI Channel State Information-   CSI-RS Channel State Information-Reference Signal-   CQI Channel Quality Indicator-   CSS Common Search Space-   CU Central Unit-   DC Dual Connectivity-   DCCH Dedicated Control Channel-   DCI Downlink Control Information-   DL Downlink-   DL-SCH Downlink Shared CHannel-   DM-RS DeModulation Reference Signal-   DRB Data Radio Bearer-   DRX Discontinuous Reception-   DTCH Dedicated Traffic Channel-   DU Distributed Unit-   EPC Evolved Packet Core-   E-UTRA Evolved UMTS Terrestrial Radio Access-   E-UTRAN Evolved-Universal Terrestrial Radio Access Network-   FDD Frequency Division Duplex-   FPGA Field Programmable Gate Arrays-   F1-C F1-Control plane-   F1-U F1-User plane-   gNB next generation Node B-   HARQ Hybrid Automatic Repeat reQuest-   HDL Hardware Description Languages-   IE Information Element-   IP Internet Protocol-   LCID Logical Channel Identifier-   LTE Long Term Evolution-   MAC Media Access Control-   MCG Master Cell Group-   MCS Modulation and Coding Scheme-   MeNB Master evolved Node B-   MIB Master Information Block-   MME Mobility Management Entity-   MN Master Node-   NACK Negative Acknowledgement-   NAS Non-Access Stratum-   NG CP Next Generation Control Plane-   NGC Next Generation Core-   NG-C NG-Control plane-   ng-eNB next generation evolved Node B-   NG-U NG-User plane-   NR New Radio-   NR MAC New Radio MAC-   NR PDCP New Radio PDCP-   NR PHY New Radio PHYsical-   NR RLC New Radio RLC-   NR RRC New Radio RRC-   NSSAI Network Slice Selection Assistance Information-   O&M Operation and Maintenance-   OFDM Orthogonal Frequency Division Multiplexing-   PBCH Physical Broadcast CHannel-   PCC Primary Component Carrier-   PCCH Paging Control CHannel-   PCell Primary Cell-   PCH Paging CHannel-   PDCCH Physical Downlink Control CHannel-   PDCP Packet Data Convergence Protocol-   PDSCH Physical Downlink Shared CHannel-   PDU Protocol Data Unit-   PHICH Physical HARQ Indicator CHannel-   PHY PHYsical-   PLMN Public Land Mobile Network-   PMI Precoding Matrix Indicator-   PRACH Physical Random Access CHannel-   PRB Physical Resource Block-   PSCell Primary Secondary Cell-   PSS Primary Synchronization Signal-   pTAG primary Timing Advance Group-   PT-RS Phase Tracking Reference Signal-   PUCCH Physical Uplink Control CHannel-   PUSCH Physical Uplink Shared CHannel-   QAM Quadrature Amplitude Modulation-   QFI Quality of Service Indicator-   QoS Quality of Service-   QPSK Quadrature Phase Shift Keying-   RA Random Access-   RACH Random Access CHannel-   RAN Radio Access Network-   RAT Radio Access Technology-   RA-RNTI Random Access-Radio Network Temporary Identifier-   RB Resource Blocks-   RBG Resource Block Groups-   RI Rank indicator-   RLC Radio Link Control-   RRC Radio Resource Control-   RS Reference Signal-   RSRP Reference Signal Received Power-   SCC Secondary Component Carrier-   SCell Secondary Cell-   SCG Secondary Cell Group-   SC-FDMA Single Carrier-Frequency Division Multiple Access-   SDAP Service Data Adaptation Protocol-   SDU Service Data Unit-   SeNB Secondary evolved Node B-   SFN System Frame Number-   S-GW Serving GateWay-   SI System Information-   SIB System Information Block-   SMF Session Management Function-   SN Secondary Node-   SpCell Special Cell-   SRB Signaling Radio Bearer-   SRS Sounding Reference Signal-   SS Synchronization Signal-   SSS Secondary Synchronization Signal-   sTAG secondary Timing Advance Group-   TA Timing Advance-   TAG Timing Advance Group-   TAI Tracking Area Identifier-   TAT Time Alignment Timer-   TB Transport Block-   TC-RNTI Temporary Cell-Radio Network Temporary Identifier-   TDD Time Division Duplex-   TDMA Time Division Multiple Access-   TTI Transmission Time Interval-   UCI Uplink Control Information-   UE User Equipment-   UL Uplink-   UL-SCH Uplink Shared CHannel-   UPF User Plane Function-   UPGW User Plane Gateway-   VHDL VHSIC Hardware Description Language-   Xn-C Xn-Control plane-   Xn-U Xn-User plane

Examples described herein may be implemented using various physicallayer modulation and transmission mechanisms. Example transmissionmechanisms may include, but are not limited to: Code Division MultipleAccess (CDMA), Orthogonal Frequency Division Multiple Access (OFDMA),Time Division Multiple Access (TDMA), Wavelet technologies, and/or thelike. Hybrid transmission mechanisms such as TDMA/CDMA, and/or OFDM/CDMAmay be used. Various modulation schemes may be used for signaltransmission in the physical layer. Examples of modulation schemesinclude, but are not limited to: phase, amplitude, code, a combinationof these, and/or the like. An example radio transmission method mayimplement Quadrature Amplitude Modulation (QAM) using Binary Phase ShiftKeying (BPSK), Quadrature Phase Shift Keying (QPSK), 16-QAM, 64-QAM,256-QAM, and/or the like. Physical radio transmission may be enhanced bydynamically or semi-dynamically changing the modulation and codingscheme, for example, depending on transmission requirements and/or radioconditions.

FIG. 1 shows an example Radio Access Network (RAN) architecture. A RANnode may comprise a next generation Node B (gNB) (e.g., 120A, 120B)providing New Radio (NR) user plane and control plane protocolterminations towards a first wireless device (e.g., 110A). A RAN nodemay comprise a base station such as a next generation evolved Node B(ng-eNB) (e.g., 120C, 120D), providing Evolved UMTS Terrestrial RadioAccess (E-UTRA) user plane and control plane protocol terminationstowards a second wireless device (e.g., 110B). A first wireless device110A may communicate with a base station, such as a gNB 120A, over a Uuinterface. A second wireless device 110B may communicate with a basestation, such as an ng-eNB 120D, over a Uu interface.

A base station, such as a gNB (e.g., 120A, 120B, etc.) and/or an ng-eNB(e.g., 120C, 120D, etc.) may host functions such as radio resourcemanagement and scheduling, IP header compression, encryption andintegrity protection of data, selection of Access and MobilityManagement Function (AMF) at wireless device (e.g., User Equipment (UE))attachment, routing of user plane and control plane data, connectionsetup and release, scheduling and transmission of paging messages (e.g.,originated from the AMF), scheduling and transmission of systembroadcast information (e.g., originated from the AMF or Operation andMaintenance (O&M)), measurement and measurement reporting configuration,transport level packet marking in the uplink, session management,support of network slicing, Quality of Service (QoS) flow management andmapping to data radio bearers, support of wireless devices in aninactive state (e.g., RRC_INACTIVE state), distribution function forNon-Access Stratum (NAS) messages, RAN sharing, dual connectivity,and/or tight interworking between NR and E-UTRA.

One or more first base stations (e.g., gNBs 120A and 120B) and/or one ormore second base stations (e.g., ng-eNBs 120C and 120D) may beinterconnected with each other via Xn interface. A first base station(e.g., gNB 120A, 120B, etc.) or a second base station (e.g., ng-eNB120C, 120D, etc.) may be connected via NG interfaces to a network, suchas a 5G Core Network (5GC). A 5GC may comprise one or more AMF/User PlanFunction (UPF) functions (e.g., 130A and/or 130B). A base station (e.g.,a gNB and/or an ng-eNB) may be connected to a UPF via an NG-User plane(NG-U) interface. The NG-U interface may provide delivery (e.g.,non-guaranteed delivery) of user plane Protocol Data Units (PDUs)between a RAN node and the UPF. A base station (e.g., a gNB and/or anng-eNB) may be connected to an AMF via an NG-Control plane (NG-C)interface. The NG-C interface may provide functions such as NG interfacemanagement, wireless device (e.g., UE) context management, wirelessdevice (e.g., UE) mobility management, transport of NAS messages,paging, PDU session management, configuration transfer, and/or warningmessage transmission.

A UPF may host functions such as anchor point for intra-/inter-RadioAccess Technology (RAT) mobility (e.g., if applicable), external PDUsession point of interconnect to data network, packet routing andforwarding, packet inspection and user plane part of policy ruleenforcement, traffic usage reporting, uplink classifier to supportrouting traffic flows to a data network, branching point to supportmulti-homed PDU session, quality of service (QoS) handling for userplane, packet filtering, gating, Uplink (UL)/Downlink (DL) rateenforcement, uplink traffic verification (e.g., Service Data Flow (SDF)to QoS flow mapping), downlink packet buffering, and/or downlink datanotification triggering.

An AMF may host functions such as NAS signaling termination, NASsignaling security, Access Stratum (AS) security control, inter CoreNetwork (CN) node signaling (e.g., for mobility between 3rd GenerationPartnership Project (3GPP) access networks), idle mode wireless devicereachability (e.g., control and execution of paging retransmission),registration area management, support of intra-system and inter-systemmobility, access authentication, access authorization including check ofroaming rights, mobility management control (e.g., subscription and/orpolicies), support of network slicing, and/or Session ManagementFunction (SMF) selection.

FIG. 2A shows an example user plane protocol stack. A Service DataAdaptation Protocol (SDAP) (e.g., 211 and 221), Packet Data ConvergenceProtocol (PDCP) (e.g., 212 and 222), Radio Link Control (RLC) (e.g., 213and 223), and Media Access Control (MAC) (e.g., 214 and 224) sublayers,and a Physical (PHY) (e.g., 215 and 225) layer, may be terminated in awireless device (e.g., 110) and in a base station (e.g., 120) on anetwork side. A PHY layer may provide transport services to higherlayers (e.g., MAC, RRC, etc.). Services and/or functions of a MACsublayer may comprise mapping between logical channels and transportchannels, multiplexing and/or demultiplexing of MAC Service Data Units(SDUs) belonging to the same or different logical channels into and/orfrom Transport Blocks (TBs) delivered to and/or from the PHY layer,scheduling information reporting, error correction through HybridAutomatic Repeat request (HARQ) (e.g., one HARQ entity per carrier forCarrier Aggregation (CA)), priority handling between wireless devicessuch as by using dynamic scheduling, priority handling between logicalchannels of a wireless device such as by using logical channelprioritization, and/or padding. A MAC entity may support one or multiplenumerologies and/or transmission timings. Mapping restrictions in alogical channel prioritization may control which numerology and/ortransmission timing a logical channel may use. An RLC sublayer maysupport transparent mode (TM), unacknowledged mode (UM), and/oracknowledged mode (AM) transmission modes. The RLC configuration may beper logical channel with no dependency on numerologies and/orTransmission Time Interval (TTI) durations. Automatic Repeat Request(ARQ) may operate on any of the numerologies and/or TTI durations withwhich the logical channel is configured. Services and functions of thePDCP layer for the user plane may comprise, for example, sequencenumbering, header compression and decompression, transfer of user data,reordering and duplicate detection, PDCP PDU routing (e.g., such as forsplit bearers), retransmission of PDCP SDUs, ciphering, deciphering andintegrity protection, PDCP SDU discard, PDCP re-establishment and datarecovery for RLC AM, and/or duplication of PDCP PDUs. Services and/orfunctions of SDAP may comprise, for example, mapping between a QoS flowand a data radio bearer. Services and/or functions of SDAP may comprisemapping a Quality of Service Indicator (QFI) in DL and UL packets. Aprotocol entity of SDAP may be configured for an individual PDU session.

FIG. 2B shows an example control plane protocol stack. A PDCP (e.g., 233and 242), RLC (e.g., 234 and 243), and MAC (e.g., 235 and 244)sublayers, and a PHY (e.g., 236 and 245) layer, may be terminated in awireless device (e.g., 110), and in a base station (e.g., 120) on anetwork side, and perform service and/or functions described above. RRC(e.g., 232 and 241) may be terminated in a wireless device and a basestation on a network side. Services and/or functions of RRC may comprisebroadcast of system information related to AS and/or NAS; paging (e.g.,initiated by a 5GC or a RAN); establishment, maintenance, and/or releaseof an RRC connection between the wireless device and RAN; securityfunctions such as key management, establishment, configuration,maintenance, and/or release of Signaling Radio Bearers (SRBs) and DataRadio Bearers (DRBs); mobility functions; QoS management functions;wireless device measurement reporting and control of the reporting;detection of and recovery from radio link failure; and/or NAS messagetransfer to/from NAS from/to a wireless device. NAS control protocol(e.g., 231 and 251) may be terminated in the wireless device and AMF(e.g., 130) on a network side. NAS control protocol may performfunctions such as authentication, mobility management between a wirelessdevice and an AMF (e.g., for 3GPP access and non-3GPP access), and/orsession management between a wireless device and an SMF (e.g., for 3GPPaccess and non-3GPP access).

A base station may configure a plurality of logical channels for awireless device. A logical channel of the plurality of logical channelsmay correspond to a radio bearer. The radio bearer may be associatedwith a QoS requirement. A base station may configure a logical channelto be mapped to one or more TTIs and/or numerologies in a plurality ofTTIs and/or numerologies. The wireless device may receive DownlinkControl Information (DCI) via a Physical Downlink Control CHannel(PDCCH) indicating an uplink grant. The uplink grant may be for a firstTTI and/or a first numerology and may indicate uplink resources fortransmission of a transport block. The base station may configure eachlogical channel in the plurality of logical channels with one or moreparameters to be used by a logical channel prioritization procedure atthe MAC layer of the wireless device. The one or more parameters maycomprise, for example, priority, prioritized bit rate, etc. A logicalchannel in the plurality of logical channels may correspond to one ormore buffers comprising data associated with the logical channel. Thelogical channel prioritization procedure may allocate the uplinkresources to one or more first logical channels in the plurality oflogical channels and/or to one or more MAC Control Elements (CEs). Theone or more first logical channels may be mapped to the first TTI and/orthe first numerology. The MAC layer at the wireless device may multiplexone or more MAC CEs and/or one or more MAC SDUs (e.g., logical channel)in a MAC PDU (e.g., transport block). The MAC PDU may comprise a MACheader comprising a plurality of MAC sub-headers. A MAC sub-header inthe plurality of MAC sub-headers may correspond to a MAC CE or a MAC SUD(e.g., logical channel) in the one or more MAC CEs and/or in the one ormore MAC SDUs. A MAC CE and/or a logical channel may be configured witha Logical Channel IDentifier (LCID). An LCID for a logical channeland/or a MAC CE may be fixed and/or pre-configured. An LCID for alogical channel and/or MAC CE may be configured for the wireless deviceby the base station. The MAC sub-header corresponding to a MAC CE and/ora MAC SDU may comprise an LCID associated with the MAC CE and/or the MACSDU.

A base station may activate, deactivate, and/or impact one or moreprocesses (e.g., set values of one or more parameters of the one or moreprocesses or start and/or stop one or more timers of the one or moreprocesses) at the wireless device, for example, by using one or more MACcommands. The one or more MAC commands may comprise one or more MACcontrol elements. The one or more processes may comprise activationand/or deactivation of PDCP packet duplication for one or more radiobearers. The base station may send (e.g., transmit) a MAC CE comprisingone or more fields. The values of the fields may indicate activationand/or deactivation of PDCP duplication for the one or more radiobearers. The one or more processes may comprise Channel StateInformation (CSI) transmission for one or more cells. The base stationmay send (e.g., transmit) one or more MAC CEs indicating activationand/or deactivation of the CSI transmission on the one or more cells.The one or more processes may comprise activation and/or deactivation ofone or more secondary cells. The base station may send (e.g., transmit)a MA CE indicating activation and/or deactivation of one or moresecondary cells. The base station may send (e.g., transmit) one or moreMAC CEs indicating starting and/or stopping of one or more DiscontinuousReception (DRX) timers at the wireless device. The base station may send(e.g., transmit) one or more MAC CEs indicating one or more timingadvance values for one or more Timing Advance Groups (TAGs).

FIG. 3 shows an example of base stations (base station 1, 120A, and basestation 2, 120B) and a wireless device 110. The wireless device 110 maycomprise a UE or any other wireless device. The base station (e.g.,120A, 120B) may comprise a Node B, eNB, gNB, ng-eNB, or any other basestation. A wireless device and/or a base station may perform one or morefunctions of a relay node. The base station 1, 120A, may comprise atleast one communication interface 320A (e.g., a wireless modem, anantenna, a wired modem, and/or the like), at least one processor 321A,and at least one set of program code instructions 323A that may bestored in non-transitory memory 322A and executable by the at least oneprocessor 321A. The base station 2, 120B, may comprise at least onecommunication interface 320B, at least one processor 321B, and at leastone set of program code instructions 323B that may be stored innon-transitory memory 322B and executable by the at least one processor321B.

A base station may comprise any number of sectors, for example: 1, 2, 3,4, or 6 sectors. A base station may comprise any number of cells, forexample, ranging from 1 to 50 cells or more. A cell may be categorized,for example, as a primary cell or secondary cell. At Radio ResourceControl (RRC) connection establishment, re-establishment, handover,etc., a serving cell may provide NAS (non-access stratum) mobilityinformation (e.g., Tracking Area Identifier (TAI)). At RRC connectionre-establishment and/or handover, a serving cell may provide securityinput. This serving cell may be referred to as the Primary Cell (PCell).In the downlink, a carrier corresponding to the PCell may be a DLPrimary Component Carrier (PCC). In the uplink, a carrier may be an ULPCC. Secondary Cells (SCells) may be configured to form together with aPCell a set of serving cells, for example, depending on wireless devicecapabilities. In a downlink, a carrier corresponding to an SCell may bea downlink secondary component carrier (DL SCC). In an uplink, a carriermay be an uplink secondary component carrier (UL SCC). An SCell may ormay not have an uplink carrier.

A cell, comprising a downlink carrier and optionally an uplink carrier,may be assigned a physical cell ID and/or a cell index. A carrier(downlink and/or uplink) may belong to one cell. The cell ID and/or cellindex may identify the downlink carrier and/or uplink carrier of thecell (e.g., depending on the context it is used). A cell ID may beequally referred to as a carrier ID, and a cell index may be referred toas a carrier index. A physical cell ID and/or a cell index may beassigned to a cell. A cell ID may be determined using a synchronizationsignal transmitted via a downlink carrier. A cell index may bedetermined using RRC messages. A first physical cell ID for a firstdownlink carrier may indicate that the first physical cell ID is for acell comprising the first downlink carrier. The same concept may beused, for example, with carrier activation and/or deactivation (e.g.,secondary cell activation and/or deactivation). A first carrier that isactivated may indicate that a cell comprising the first carrier isactivated.

A base station may send (e.g., transmit) to a wireless device one ormore messages (e.g., RRC messages) comprising a plurality ofconfiguration parameters for one or more cells. One or more cells maycomprise at least one primary cell and at least one secondary cell. AnRRC message may be broadcasted and/or unicasted to the wireless device.Configuration parameters may comprise common parameters and dedicatedparameters.

Services and/or functions of an RRC sublayer may comprise at least oneof: broadcast of system information related to AS and/or NAS; paginginitiated by a 5GC and/or an NG-RAN; establishment, maintenance, and/orrelease of an RRC connection between a wireless device and an NG-RAN,which may comprise at least one of addition, modification, and/orrelease of carrier aggregation; and/or addition, modification, and/orrelease of dual connectivity in NR or between E-UTRA and NR. Servicesand/or functions of an RRC sublayer may comprise at least one ofsecurity functions comprising key management; establishment,configuration, maintenance, and/or release of Signaling Radio Bearers(SRBs) and/or Data Radio Bearers (DRBs); mobility functions which maycomprise at least one of a handover (e.g., intra NR mobility orinter-RAT mobility) and/or a context transfer; and/or a wireless devicecell selection and/or reselection and/or control of cell selection andreselection. Services and/or functions of an RRC sublayer may compriseat least one of QoS management functions; a wireless device measurementconfiguration/reporting; detection of and/or recovery from radio linkfailure; and/or NAS message transfer to and/or from a core networkentity (e.g., AMF, Mobility Management Entity (MME)) from and/or to thewireless device.

An RRC sublayer may support an RRC_Idle state, an RRC_Inactive state,and/or an RRC_Connected state for a wireless device. In an RRC_Idlestate, a wireless device may perform at least one of: Public Land MobileNetwork (PLMN) selection; receiving broadcasted system information; cellselection and/or re-selection; monitoring and/or receiving a paging formobile terminated data initiated by 5GC; paging for mobile terminateddata area managed by 5GC; and/or DRX for CN paging configured via NAS.In an RRC_Inactive state, a wireless device may perform at least one of:receiving broadcasted system information; cell selection and/orre-selection; monitoring and/or receiving a RAN and/or CN paginginitiated by an NG-RAN and/or a 5GC; RAN-based notification area (RNA)managed by an NG-RAN; and/or DRX for a RAN and/or CN paging configuredby NG-RAN/NAS. In an RRC_Idle state of a wireless device, a base station(e.g., NG-RAN) may keep a 5GC-NG-RAN connection (e.g., both C/U-planes)for the wireless device; and/or store a wireless device AS context forthe wireless device. In an RRC_Connected state of a wireless device, abase station (e.g., NG-RAN) may perform at least one of: establishmentof 5GC-NG-RAN connection (both C/U-planes) for the wireless device;storing a UE AS context for the wireless device; send (e.g., transmit)and/or receive of unicast data to and/or from the wireless device;and/or network-controlled mobility based on measurement results receivedfrom the wireless device. In an RRC_Connected state of a wirelessdevice, an NG-RAN may know a cell to which the wireless device belongs.

System information (SI) may be divided into minimum SI and other SI. Theminimum SI may be periodically broadcast. The minimum SI may comprisebasic information required for initial access and/or information foracquiring any other SI broadcast periodically and/or provisionedon-demand (e.g., scheduling information). The other SI may either bebroadcast, and/or be provisioned in a dedicated manner, such as eithertriggered by a network and/or upon request from a wireless device. Aminimum SI may be transmitted via two different downlink channels usingdifferent messages (e.g., MasterInformationBlock andSystemInformationBlockType1). Another SI may be transmitted viaSystemInformationBlockType2. For a wireless device in an RRC_Connectedstate, dedicated RRC signaling may be used for the request and deliveryof the other SI. For the wireless device in the RRC_Idle state and/or inthe RRC_Inactive state, the request may trigger a random-accessprocedure.

A wireless device may report its radio access capability information,which may be static. A base station may request one or more indicationsof capabilities for a wireless device to report based on bandinformation. A temporary capability restriction request may be sent bythe wireless device (e.g., if allowed by a network) to signal thelimited availability of some capabilities (e.g., due to hardwaresharing, interference, and/or overheating) to the base station. The basestation may confirm or reject the request. The temporary capabilityrestriction may be transparent to 5GC (e.g., static capabilities may bestored in 5GC).

A wireless device may have an RRC connection with a network, forexample, if CA is configured. At RRC connection establishment,re-establishment, and/or handover procedures, a serving cell may provideNAS mobility information. At RRC connection re-establishment and/orhandover, a serving cell may provide a security input. This serving cellmay be referred to as the PCell. SCells may be configured to formtogether with the PCell a set of serving cells, for example, dependingon the capabilities of the wireless device. The configured set ofserving cells for the wireless device may comprise a PCell and one ormore SCells.

The reconfiguration, addition, and/or removal of SCells may be performedby RRC messaging. At intra-NR handover, RRC may add, remove, and/orreconfigure SCells for usage with the target PCell. Dedicated RRCsignaling may be used (e.g., if adding a new SCell) to send all requiredsystem information of the SCell (e.g., if in connected mode, wirelessdevices may not acquire broadcasted system information directly from theSCells).

The purpose of an RRC connection reconfiguration procedure may be tomodify an RRC connection, (e.g., to establish, modify, and/or releaseRBs; to perform handover; to setup, modify, and/or release measurements,for example, to add, modify, and/or release SCells and cell groups). NASdedicated information may be transferred from the network to thewireless device, for example, as part of the RRC connectionreconfiguration procedure. The RRCConnectionReconfiguration message maybe a command to modify an RRC connection. One or more RRC messages mayconvey information for measurement configuration, mobility control,and/or radio resource configuration (e.g., RBs, MAC main configuration,and/or physical channel configuration), which may comprise anyassociated dedicated NAS information and/or security configuration. Thewireless device may perform an SCell release, for example, if thereceived RRC Connection Reconfiguration message includes thesCellToReleaseList. The wireless device may perform SCell additions ormodification, for example, if the received RRC ConnectionReconfiguration message includes the sCellToAddModList.

An RRC connection establishment, reestablishment, and/or resumeprocedure may be to establish, reestablish, and/or resume an RRCconnection, respectively. An RRC connection establishment procedure maycomprise SRB1 establishment. The RRC connection establishment proceduremay be used to transfer the initial NAS dedicated information and/ormessage from a wireless device to an E-UTRAN. TheRRCConnectionReestablishment message may be used to re-establish SRB1.

A measurement report procedure may be used to transfer measurementresults from a wireless device to an NG-RAN. The wireless device mayinitiate a measurement report procedure, for example, after successfulsecurity activation. A measurement report message may be used to send(e.g., transmit) measurement results.

The wireless device 110 may comprise at least one communicationinterface 310 (e.g., a wireless modem, an antenna, and/or the like), atleast one processor 314, and at least one set of program codeinstructions 316 that may be stored in non-transitory memory 315 andexecutable by the at least one processor 314. The wireless device 110may further comprise at least one of at least one speaker and/ormicrophone 311, at least one keypad 312, at least one display and/ortouchpad 313, at least one power source 317, at least one globalpositioning system (GPS) chipset 318, and/or other peripherals 319.

The processor 314 of the wireless device 110, the processor 321A of thebase station 1 120A, and/or the processor 321B of the base station 2120B may comprise at least one of a general-purpose processor, a digitalsignal processor (DSP), a controller, a microcontroller, an applicationspecific integrated circuit (ASIC), a field programmable gate array(FPGA) and/or other programmable logic device, discrete gate and/ortransistor logic, discrete hardware components, and/or the like. Theprocessor 314 of the wireless device 110, the processor 321A in basestation 1 120A, and/or the processor 321B in base station 2 120B mayperform at least one of signal coding and/or processing, dataprocessing, power control, input/output processing, and/or any otherfunctionality that may enable the wireless device 110, the base station1 120A and/or the base station 2 120B to operate in a wirelessenvironment.

The processor 314 of the wireless device 110 may be connected to and/orin communication with the speaker and/or microphone 311, the keypad 312,and/or the display and/or touchpad 313. The processor 314 may receiveuser input data from and/or provide user output data to the speakerand/or microphone 311, the keypad 312, and/or the display and/ortouchpad 313. The processor 314 in the wireless device 110 may receivepower from the power source 317 and/or may be configured to distributethe power to the other components in the wireless device 110. The powersource 317 may comprise at least one of one or more dry cell batteries,solar cells, fuel cells, and/or the like. The processor 314 may beconnected to the GPS chipset 318. The GPS chipset 318 may be configuredto provide geographic location information of the wireless device 110.

The processor 314 of the wireless device 110 may further be connected toand/or in communication with other peripherals 319, which may compriseone or more software and/or hardware modules that may provide additionalfeatures and/or functionalities. For example, the peripherals 319 maycomprise at least one of an accelerometer, a satellite transceiver, adigital camera, a universal serial bus (USB) port, a hands-free headset,a frequency modulated (FM) radio unit, a media player, an Internetbrowser, and/or the like.

The communication interface 320A of the base station 1, 120A, and/or thecommunication interface 320B of the base station 2, 120B, may beconfigured to communicate with the communication interface 310 of thewireless device 110, for example, via a wireless link 330A and/or via awireless link 330B, respectively. The communication interface 320A ofthe base station 1, 120A, may communicate with the communicationinterface 320B of the base station 2 and/or other RAN and/or corenetwork nodes.

The wireless link 330A and/or the wireless link 330B may comprise atleast one of a bi-directional link and/or a directional link. Thecommunication interface 310 of the wireless device 110 may be configuredto communicate with the communication interface 320A of the base station1 120A and/or with the communication interface 320B of the base station2 120B. The base station 1 120A and the wireless device 110, and/or thebase station 2 120B and the wireless device 110, may be configured tosend and receive transport blocks, for example, via the wireless link330A and/or via the wireless link 330B, respectively. The wireless link330A and/or the wireless link 330B may use at least one frequencycarrier. Transceiver(s) may be used. A transceiver may be a device thatcomprises both a transmitter and a receiver. Transceivers may be used indevices such as wireless devices, base stations, relay nodes, computingdevices, and/or the like. Radio technology may be implemented in thecommunication interface 310, 320A, and/or 320B, and the wireless link330A and/or 330B. The radio technology may comprise one or more elementsshown in FIG. 4A, FIG. 4B, FIG. 4C, FIG. 4D, FIG. 6, FIG. 7A, FIG. 7B,FIG. 8, and associated text, described below.

Other nodes in a wireless network (e.g. AMF, UPF, SMF, etc.) maycomprise one or more communication interfaces, one or more processors,and memory storing instructions. A node (e.g., wireless device, basestation, AMF, SMF, UPF, servers, switches, antennas, and/or the like)may comprise one or more processors, and memory storing instructionsthat when executed by the one or more processors causes the node toperform certain processes and/or functions. Single-carrier and/ormulti-carrier communication operation may be performed. A non-transitorytangible computer readable media may comprise instructions executable byone or more processors to cause operation of single-carrier and/ormulti-carrier communications. An article of manufacture may comprise anon-transitory tangible computer readable machine-accessible mediumhaving instructions encoded thereon for enabling programmable hardwareto cause a node to enable operation of single-carrier and/ormulti-carrier communications. The node may include processors, memory,interfaces, and/or the like.

An interface may comprise at least one of a hardware interface, afirmware interface, a software interface, and/or a combination thereof.The hardware interface may comprise connectors, wires, and/or electronicdevices such as drivers, amplifiers, and/or the like. The softwareinterface may comprise code stored in a memory device to implementprotocol(s), protocol layers, communication drivers, device drivers,combinations thereof, and/or the like. The firmware interface maycomprise a combination of embedded hardware and/or code stored in(and/or in communication with) a memory device to implement connections,electronic device operations, protocol(s), protocol layers,communication drivers, device drivers, hardware operations, combinationsthereof, and/or the like.

A communication network may comprise the wireless device 110, the basestation 1, 120A, the base station 2, 120B, and/or any other device. Thecommunication network may comprise any number and/or type of devices,such as, for example, computing devices, wireless devices, mobiledevices, handsets, tablets, laptops, internet of things (IoT) devices,hotspots, cellular repeaters, computing devices, and/or, more generally,user equipment (e.g., UE). Although one or more of the above types ofdevices may be referenced herein (e.g., UE, wireless device, computingdevice, etc.), it should be understood that any device herein maycomprise any one or more of the above types of devices or similardevices. The communication network, and any other network referencedherein, may comprise an LTE network, a 5G network, or any other networkfor wireless communications. Apparatuses, systems, and/or methodsdescribed herein may generally be described as implemented on one ormore devices (e.g., wireless device, base station, eNB, gNB, computingdevice, etc.), in one or more networks, but it will be understood thatone or more features and steps may be implemented on any device and/orin any network. As used throughout, the term “base station” may compriseone or more of: a base station, a node, a Node B, a gNB, an eNB, anng-eNB, a relay node (e.g., an integrated access and backhaul (IAB)node), a donor node (e.g., a donor eNB, a donor gNB, etc.), an accesspoint (e.g., a WiFi access point), a computing device, a device capableof wirelessly communicating, or any other device capable of sendingand/or receiving signals. As used throughout, the term “wireless device”may comprise one or more of: a UE, a handset, a mobile device, acomputing device, a node, a device capable of wirelessly communicating,or any other device capable of sending and/or receiving signals. Anyreference to one or more of these terms/devices also considers use ofany other term/device mentioned above.

FIG. 4A, FIG. 4B, FIG. 4C and FIG. 4D show examples of uplink anddownlink signal transmission. FIG. 4A shows an example uplinktransmitter for at least one physical channel. A baseband signalrepresenting a physical uplink shared channel may perform one or morefunctions. The one or more functions may comprise at least one of:scrambling (e.g., by Scrambling); modulation of scrambled bits togenerate complex-valued symbols (e.g., by a Modulation mapper); mappingof the complex-valued modulation symbols onto one or severaltransmission layers (e.g., by a Layer mapper); transform precoding togenerate complex-valued symbols (e.g., by a Transform precoder);precoding of the complex-valued symbols (e.g., by a Precoder); mappingof precoded complex-valued symbols to resource elements (e.g., by aResource element mapper); generation of complex-valued time-domainSingle Carrier-Frequency Division Multiple Access (SC-FDMA) or CP-OFDMsignal for an antenna port (e.g., by a signal gen.); and/or the like. ASC-FDMA signal for uplink transmission may be generated, for example, iftransform precoding is enabled. A CP-OFDM signal for uplink transmissionmay be generated by FIG. 4A, for example, if transform precoding is notenabled. These functions are shown as examples and other mechanisms maybe implemented.

FIG. 4B shows an example of modulation and up-conversion to the carrierfrequency of a complex-valued SC-FDMA or CP-OFDM baseband signal for anantenna port and/or for the complex-valued Physical Random AccessCHannel (PRACH) baseband signal. Filtering may be performed prior totransmission.

FIG. 4C shows an example of downlink transmissions. The baseband signalrepresenting a downlink physical channel may perform one or morefunctions. The one or more functions may comprise: scrambling of codedbits in a codeword to be transmitted on a physical channel (e.g., byScrambling); modulation of scrambled bits to generate complex-valuedmodulation symbols (e.g., by a Modulation mapper); mapping of thecomplex-valued modulation symbols onto one or several transmissionlayers (e.g., by a Layer mapper); precoding of the complex-valuedmodulation symbols on a layer for transmission on the antenna ports(e.g., by Precoding); mapping of complex-valued modulation symbols foran antenna port to resource elements (e.g., by a Resource elementmapper); generation of complex-valued time-domain OFDM signal for anantenna port (e.g., by an OFDM signal gen.); and/or the like. Thesefunctions are shown as examples and other mechanisms may be implemented.

A base station may send (e.g., transmit) a first symbol and a secondsymbol on an antenna port, to a wireless device. The wireless device mayinfer the channel (e.g., fading gain, multipath delay, etc.) forconveying the second symbol on the antenna port, from the channel forconveying the first symbol on the antenna port. A first antenna port anda second antenna port may be quasi co-located, for example, if one ormore large-scale properties of the channel over which a first symbol onthe first antenna port is conveyed may be inferred from the channel overwhich a second symbol on a second antenna port is conveyed. The one ormore large-scale properties may comprise at least one of: delay spread;Doppler spread; Doppler shift; average gain; average delay; and/orspatial receiving (Rx) parameters.

FIG. 4D shows an example modulation and up-conversion to the carrierfrequency of the complex-valued OFDM baseband signal for an antennaport. Filtering may be performed prior to transmission.

FIG. 5A shows example uplink channel mapping and example uplink physicalsignals. A physical layer may provide one or more information transferservices to a MAC and/or one or more higher layers. The physical layermay provide the one or more information transfer services to the MAC viaone or more transport channels. An information transfer service mayindicate how and/or with what characteristics data is transferred overthe radio interface.

Uplink transport channels may comprise an Uplink-Shared CHannel (UL-SCH)501 and/or a Random Access CHannel (RACH) 502. A wireless device maysend (e.g., transmit) one or more uplink DM-RSs 506 to a base stationfor channel estimation, for example, for coherent demodulation of one ormore uplink physical channels (e.g., PUSCH 503 and/or PUCCH 504). Thewireless device may send (e.g., transmit) to a base station at least oneuplink DM-RS 506 with PUSCH 503 and/or PUCCH 504, wherein the at leastone uplink DM-RS 506 may be spanning a same frequency range as acorresponding physical channel. The base station may configure thewireless device with one or more uplink DM-RS configurations. At leastone DM-RS configuration may support a front-loaded DM-RS pattern. Afront-loaded DM-RS may be mapped over one or more OFDM symbols (e.g., 1or 2 adjacent OFDM symbols). One or more additional uplink DM-RS may beconfigured to send (e.g., transmit) at one or more symbols of a PUSCHand/or PUCCH. The base station may semi-statically configure thewireless device with a maximum number of front-loaded DM-RS symbols forPUSCH and/or PUCCH. The wireless device may schedule a single-symbolDM-RS and/or double symbol DM-RS based on a maximum number offront-loaded DM-RS symbols, wherein the base station may configure thewireless device with one or more additional uplink DM-RS for PUSCHand/or PUCCH. A new radio network may support, for example, at least forCP-OFDM, a common DM-RS structure for DL and UL, wherein a DM-RSlocation, DM-RS pattern, and/or scrambling sequence may be same ordifferent.

Whether or not an uplink PT-RS 507 is present may depend on an RRCconfiguration. A presence of the uplink PT-RS may be wirelessdevice-specifically configured. A presence and/or a pattern of theuplink PT-RS 507 in a scheduled resource may be wirelessdevice-specifically configured by a combination of RRC signaling and/orassociation with one or more parameters used for other purposes (e.g.,Modulation and Coding Scheme (MCS)) which may be indicated by DCI. Ifconfigured, a dynamic presence of uplink PT-RS 507 may be associatedwith one or more DCI parameters comprising at least a MCS. A radionetwork may support a plurality of uplink PT-RS densities defined intime/frequency domain. If present, a frequency domain density may beassociated with at least one configuration of a scheduled bandwidth. Awireless device may assume a same precoding for a DMRS port and a PT-RSport. A number of PT-RS ports may be less than a number of DM-RS portsin a scheduled resource. The uplink PT-RS 507 may be confined in thescheduled time/frequency duration for a wireless device.

A wireless device may send (e.g., transmit) an SRS 508 to a base stationfor channel state estimation, for example, to support uplink channeldependent scheduling and/or link adaptation. The SRS 508 sent (e.g.,transmitted) by the wireless device may allow for the base station toestimate an uplink channel state at one or more different frequencies. Abase station scheduler may use an uplink channel state to assign one ormore resource blocks of a certain quality (e.g., above a qualitythreshold) for an uplink PUSCH transmission from the wireless device.The base station may semi-statically configure the wireless device withone or more SRS resource sets. For an SRS resource set, the base stationmay configure the wireless device with one or more SRS resources. An SRSresource set applicability may be configured by a higher layer (e.g.,RRC) parameter. An SRS resource in each of one or more SRS resource setsmay be sent (e.g., transmitted) at a time instant, for example, if ahigher layer parameter indicates beam management. The wireless devicemay send (e.g., transmit) one or more SRS resources in different SRSresource sets simultaneously. A new radio network may support aperiodic,periodic, and/or semi-persistent SRS transmissions. The wireless devicemay send (e.g., transmit) SRS resources, for example, based on one ormore trigger types. The one or more trigger types may comprise higherlayer signaling (e.g., RRC) and/or one or more DCI formats (e.g., atleast one DCI format may be used for a wireless device to select atleast one of one or more configured SRS resource sets). An SRS triggertype 0 may refer to an SRS triggered based on a higher layer signaling.An SRS trigger type 1 may refer to an SRS triggered based on one or moreDCI formats. The wireless device may be configured to send (e.g.,transmit) the SRS 508 after a transmission of PUSCH 503 andcorresponding uplink DM-RS 506, for example, if PUSCH 503 and the SRS508 are transmitted in a same slot.

A base station may semi-statically configure a wireless device with oneor more SRS configuration parameters indicating at least one offollowing: an SRS resource configuration identifier, a number of SRSports, time domain behavior of SRS resource configuration (e.g., anindication of periodic, semi-persistent, or aperiodic SRS), slot(mini-slot, and/or subframe) level periodicity and/or offset for aperiodic and/or aperiodic SRS resource, a number of OFDM symbols in aSRS resource, starting OFDM symbol of a SRS resource, an SRS bandwidth,a frequency hopping bandwidth, a cyclic shift, and/or an SRS sequenceID.

FIG. 5B shows an example downlink channel mapping and downlink physicalsignals. Downlink transport channels may comprise a Downlink-SharedCHannel (DL-SCH) 511, a Paging CHannel (PCH) 512, and/or a BroadcastCHannel (BCH) 513. A transport channel may be mapped to one or morecorresponding physical channels. A UL-SCH 501 may be mapped to aPhysical Uplink Shared CHannel (PUSCH) 503. A RACH 502 may be mapped toa PRACH 505. A DL-SCH 511 and a PCH 512 may be mapped to a PhysicalDownlink Shared CHannel (PDSCH) 514. A BCH 513 may be mapped to aPhysical Broadcast CHannel (PBCH) 516.

A radio network may comprise one or more downlink and/or uplinktransport channels. The radio network may comprise one or more physicalchannels without a corresponding transport channel. The one or morephysical channels may be used for an Uplink Control Information (UCI)509 and/or a Downlink Control Information (DCI) 517. A Physical UplinkControl CHannel (PUCCH) 504 may carry UCI 509 from a wireless device toa base station. A Physical Downlink Control CHannel (PDCCH) 515 maycarry the DCI 517 from a base station to a wireless device. The radionetwork (e.g., NR) may support the UCI 509 multiplexing in the PUSCH503, for example, if the UCI 509 and the PUSCH 503 transmissions maycoincide in a slot (e.g., at least in part). The UCI 509 may comprise atleast one of a CSI, an Acknowledgement (ACK)/Negative Acknowledgement(NACK), and/or a scheduling request. The DCI 517 via the PDCCH 515 mayindicate at least one of following: one or more downlink assignmentsand/or one or more uplink scheduling grants.

In uplink, a wireless device may send (e.g., transmit) one or moreReference Signals (RSs) to a base station. The one or more RSs maycomprise at least one of a Demodulation-RS (DM-RS) 506, a PhaseTracking-RS (PT-RS) 507, and/or a Sounding RS (SRS) 508. In downlink, abase station may send (e.g., transmit, unicast, multicast, and/orbroadcast) one or more RSs to a wireless device. The one or more RSs maycomprise at least one of a Primary Synchronization Signal(PSS)/Secondary Synchronization Signal (SSS) 521, a CSI-RS 522, a DM-RS523, and/or a PT-RS 524.

In a time domain, an SS/PBCH block may comprise one or more OFDM symbols(e.g., 4 OFDM symbols numbered in increasing order from 0 to 3) withinthe SS/PBCH block. An SS/PBCH block may comprise the PSS/SSS 521 and/orthe PBCH 516. In the frequency domain, an SS/PBCH block may comprise oneor more contiguous subcarriers (e.g., 240 contiguous subcarriers withthe subcarriers numbered in increasing order from 0 to 239) within theSS/PBCH block. The PSS/SSS 521 may occupy, for example, 1 OFDM symboland 127 subcarriers. The PBCH 516 may span across, for example, 3 OFDMsymbols and 240 subcarriers. A wireless device may assume that one ormore SS/PBCH blocks transmitted with a same block index may be quasico-located, for example, with respect to Doppler spread, Doppler shift,average gain, average delay, and/or spatial Rx parameters. A wirelessdevice may not assume quasi co-location for other SS/PBCH blocktransmissions. A periodicity of an SS/PBCH block may be configured by aradio network (e.g., by an RRC signaling). One or more time locations inwhich the SS/PBCH block may be sent may be determined by sub-carrierspacing. A wireless device may assume a band-specific sub-carrierspacing for an SS/PBCH block, for example, unless a radio network hasconfigured the wireless device to assume a different sub-carrierspacing.

The downlink CSI-RS 522 may be used for a wireless device to acquirechannel state information. A radio network may support periodic,aperiodic, and/or semi-persistent transmission of the downlink CSI-RS522. A base station may semi-statically configure and/or reconfigure awireless device with periodic transmission of the downlink CSI-RS 522. Aconfigured CSI-RS resources may be activated and/or deactivated. Forsemi-persistent transmission, an activation and/or deactivation of aCSI-RS resource may be triggered dynamically. A CSI-RS configuration maycomprise one or more parameters indicating at least a number of antennaports. A base station may configure a wireless device with 32 ports, orany other number of ports. A base station may semi-statically configurea wireless device with one or more CSI-RS resource sets. One or moreCSI-RS resources may be allocated from one or more CSI-RS resource setsto one or more wireless devices. A base station may semi-staticallyconfigure one or more parameters indicating CSI RS resource mapping, forexample, time-domain location of one or more CSI-RS resources, abandwidth of a CSI-RS resource, and/or a periodicity. A wireless devicemay be configured to use the same OFDM symbols for the downlink CSI-RS522 and the Control Resource Set (CORESET), for example, if the downlinkCSI-RS 522 and the CORESET are spatially quasi co-located and resourceelements associated with the downlink CSI-RS 522 are the outside of PRBsconfigured for the CORESET. A wireless device may be configured to usethe same OFDM symbols for downlink CSI-RS 522 and SSB/PBCH, for example,if the downlink CSI-RS 522 and SSB/PBCH are spatially quasi co-locatedand resource elements associated with the downlink CSI-RS 522 areoutside of the PRBs configured for the SSB/PBCH.

A wireless device may send (e.g., transmit) one or more downlink DM-RSs523 to a base station for channel estimation, for example, for coherentdemodulation of one or more downlink physical channels (e.g., PDSCH514). A radio network may support one or more variable and/orconfigurable DM-RS patterns for data demodulation. At least one downlinkDM-RS configuration may support a front-loaded DM-RS pattern. Afront-loaded DM-RS may be mapped over one or more OFDM symbols (e.g., 1or 2 adjacent OFDM symbols). A base station may semi-staticallyconfigure a wireless device with a maximum number of front-loaded DM-RSsymbols for PDSCH 514. A DM-RS configuration may support one or moreDM-RS ports. A DM-RS configuration may support at least 8 orthogonaldownlink DM-RS ports, for example, for single user-MIMO. ADM-RSconfiguration may support 12 orthogonal downlink DM-RS ports, forexample, for multiuser-MIMO. A radio network may support, for example,at least for CP-OFDM, a common DM-RS structure for DL and UL, wherein aDM-RS location, DM-RS pattern, and/or scrambling sequence may be thesame or different.

Whether or not the downlink PT-RS 524 is present may depend on an RRCconfiguration. A presence of the downlink PT-RS 524 may be wirelessdevice-specifically configured. A presence and/or a pattern of thedownlink PT-RS 524 in a scheduled resource may be wirelessdevice-specifically configured, for example, by a combination of RRCsignaling and/or an association with one or more parameters used forother purposes (e.g., MCS) which may be indicated by the DCI. Ifconfigured, a dynamic presence of the downlink PT-RS 524 may beassociated with one or more DCI parameters comprising at least MCS. Aradio network may support a plurality of PT-RS densities in atime/frequency domain. If present, a frequency domain density may beassociated with at least one configuration of a scheduled bandwidth. Awireless device may assume the same precoding for a DMRS port and aPT-RS port. A number of PT-RS ports may be less than a number of DM-RSports in a scheduled resource. The downlink PT-RS 524 may be confined inthe scheduled time/frequency duration for a wireless device.

FIG. 6 shows an example transmission time and reception time for acarrier. A multicarrier OFDM communication system may include one ormore carriers, for example, ranging from 1 to 32 carriers (such as forcarrier aggregation) or ranging from 1 to 64 carriers (such as for dualconnectivity). Different radio frame structures may be supported (e.g.,for FDD and/or for TDD duplex mechanisms). FIG. 6 shows an example frametiming. Downlink and uplink transmissions may be organized into radioframes 601. Radio frame duration may be 10 milliseconds (ms). A 10 msradio frame 601 may be divided into ten equally sized subframes 602,each with a 1 ms duration. Subframe(s) may comprise one or more slots(e.g., slots 603 and 605) depending on subcarrier spacing and/or CPlength. For example, a subframe with 15 kHz, 30 kHz, 60 kHz, 120 kHz,240 kHz and 480 kHz subcarrier spacing may comprise one, two, four,eight, sixteen and thirty-two slots, respectively. In FIG. 6, a subframemay be divided into two equally sized slots 603 with 0.5 ms duration.For example, 10 subframes may be available for downlink transmission and10 subframes may be available for uplink transmissions in a 10 msinterval. Other subframe durations such as, for example, 0.5 ms, 1 ms, 2ms, and 5 ms may be supported. Uplink and downlink transmissions may beseparated in the frequency domain. Slot(s) may include a plurality ofOFDM symbols 604. The number of OFDM symbols 604 in a slot 605 maydepend on the cyclic prefix length. A slot may be 14 OFDM symbols forthe same subcarrier spacing of up to 480 kHz with normal CP. A slot maybe 12 OFDM symbols for the same subcarrier spacing of 60 kHz withextended CP. A slot may comprise downlink, uplink, and/or a downlinkpart and an uplink part, and/or alike.

FIG. 7A shows example sets of OFDM subcarriers. A base station maycommunicate with a wireless device using a carrier having an examplechannel bandwidth 700. Arrow(s) in the example may depict a subcarrierin a multicarrier OFDM system. The OFDM system may use technology suchas OFDM technology, SC-FDMA technology, and/or the like. An arrow 701shows a subcarrier transmitting information symbols. A subcarrierspacing 702, between two contiguous subcarriers in a carrier, may be anyone of 15 kHz, 30 kHz, 60 kHz, 120 kHz, 240 kHz, or any other frequency.Different subcarrier spacing may correspond to different transmissionnumerologies. A transmission numerology may comprise at least: anumerology index; a value of subcarrier spacing; and/or a type of cyclicprefix (CP). A base station may send (e.g., transmit) to and/or receivefrom a wireless device via a number of subcarriers 703 in a carrier. Abandwidth occupied by a number of subcarriers 703 (e.g., transmissionbandwidth) may be smaller than the channel bandwidth 700 of a carrier,for example, due to guard bands 704 and 705. Guard bands 704 and 705 maybe used to reduce interference to and from one or more neighborcarriers. A number of subcarriers (e.g., transmission bandwidth) in acarrier may depend on the channel bandwidth of the carrier and/or thesubcarrier spacing. A transmission bandwidth, for a carrier with a 20MHz channel bandwidth and a 15 kHz subcarrier spacing, may be in numberof 1024 subcarriers.

A base station and a wireless device may communicate with multiplecomponent carriers (CCs), for example, if configured with CA. Differentcomponent carriers may have different bandwidth and/or differentsubcarrier spacing, for example, if CA is supported. A base station maysend (e.g., transmit) a first type of service to a wireless device via afirst component carrier. The base station may send (e.g., transmit) asecond type of service to the wireless device via a second componentcarrier. Different types of services may have different servicerequirements (e.g., data rate, latency, reliability), which may besuitable for transmission via different component carriers havingdifferent subcarrier spacing and/or different bandwidth.

FIG. 7B shows examples of component carriers. A first component carriermay comprise a first number of subcarriers 706 having a first subcarrierspacing 709. A second component carrier may comprise a second number ofsubcarriers 707 having a second subcarrier spacing 710. A thirdcomponent carrier may comprise a third number of subcarriers 708 havinga third subcarrier spacing 711. Carriers in a multicarrier OFDMcommunication system may be contiguous carriers, non-contiguouscarriers, or a combination of both contiguous and non-contiguouscarriers.

FIG. 8 shows an example of OFDM radio resources. A carrier may have atransmission bandwidth 801. A resource grid may be in a structure offrequency domain 802 and time domain 803. A resource grid may comprise afirst number of OFDM symbols in a subframe and a second number ofresource blocks, starting from a common resource block indicated byhigher-layer signaling (e.g., RRC signaling), for a transmissionnumerology and a carrier. In a resource grid, a resource element 805 maycomprise a resource unit that may be identified by a subcarrier indexand a symbol index. A subframe may comprise a first number of OFDMsymbols 807 that may depend on a numerology associated with a carrier. Asubframe may have 14 OFDM symbols for a carrier, for example, if asubcarrier spacing of a numerology of a carrier is 15 kHz. A subframemay have 28 OFDM symbols, for example, if a subcarrier spacing of anumerology is 30 kHz. A subframe may have 56 OFDM symbols, for example,if a subcarrier spacing of a numerology is 60 kHz. A subcarrier spacingof a numerology may comprise any other frequency. A second number ofresource blocks comprised in a resource grid of a carrier may depend ona bandwidth and a numerology of the carrier.

A resource block 806 may comprise 12 subcarriers. Multiple resourceblocks may be grouped into a Resource Block Group (RBG) 804. A size of aRBG may depend on at least one of: a RRC message indicating a RBG sizeconfiguration; a size of a carrier bandwidth; and/or a size of abandwidth part of a carrier. A carrier may comprise multiple bandwidthparts. A first bandwidth part of a carrier may have a differentfrequency location and/or a different bandwidth from a second bandwidthpart of the carrier.

A base station may send (e.g., transmit), to a wireless device, adownlink control information comprising a downlink or uplink resourceblock assignment. A base station may send (e.g., transmit) to and/orreceive from, a wireless device, data packets (e.g., transport blocks).The data packets may be scheduled on and transmitted via one or moreresource blocks and one or more slots indicated by parameters indownlink control information and/or RRC message(s). A starting symbolrelative to a first slot of the one or more slots may be indicated tothe wireless device. A base station may send (e.g., transmit) to and/orreceive from, a wireless device, data packets. The data packets may bescheduled for transmission on one or more RBGs and in one or more slots.

A base station may send (e.g., transmit), to a wireless device, downlinkcontrol information comprising a downlink assignment. The base stationmay send (e.g., transmit) the DCI via one or more PDCCHs. The downlinkassignment may comprise parameters indicating at least one of amodulation and coding format; resource allocation; and/or HARQinformation related to the DL-SCH. The resource allocation may compriseparameters of resource block allocation; and/or slot allocation. A basestation may allocate (e.g., dynamically) resources to a wireless device,for example, via a Cell-Radio Network Temporary Identifier (C-RNTI) onone or more PDCCHs. The wireless device may monitor the one or morePDCCHs, for example, in order to find possible allocation if itsdownlink reception is enabled. The wireless device may receive one ormore downlink data packets on one or more PDSCH scheduled by the one ormore PDCCHs, for example, if the wireless device successfully detectsthe one or more PDCCHs.

A base station may allocate Configured Scheduling (CS) resources fordown link transmission to a wireless device. The base station may send(e.g., transmit) one or more RRC messages indicating a periodicity ofthe CS grant. The base station may send (e.g., transmit) DCI via a PDCCHaddressed to a Configured Scheduling-RNTI (CS-RNTI) activating the CSresources. The DCI may comprise parameters indicating that the downlinkgrant is a CS grant. The CS grant may be implicitly reused according tothe periodicity defined by the one or more RRC messages. The CS grantmay be implicitly reused, for example, until deactivated.

A base station may send (e.g., transmit), to a wireless device via oneor more PDCCHs, downlink control information comprising an uplink grant.The uplink grant may comprise parameters indicating at least one of amodulation and coding format; a resource allocation; and/or HARQinformation related to the UL-SCH. The resource allocation may compriseparameters of resource block allocation; and/or slot allocation. Thebase station may dynamically allocate resources to the wireless devicevia a C-RNTI on one or more PDCCHs. The wireless device may monitor theone or more PDCCHs, for example, in order to find possible resourceallocation. The wireless device may send (e.g., transmit) one or moreuplink data packets via one or more PUSCH scheduled by the one or morePDCCHs, for example, if the wireless device successfully detects the oneor more PDCCHs.

The base station may allocate CS resources for uplink data transmissionto a wireless device. The base station may transmit one or more RRCmessages indicating a periodicity of the CS grant. The base station maysend (e.g., transmit) DCI via a PDCCH addressed to a CS-RNTI to activatethe CS resources. The DCI may comprise parameters indicating that theuplink grant is a CS grant. The CS grant may be implicitly reusedaccording to the periodicity defined by the one or more RRC message, TheCS grant may be implicitly reused, for example, until deactivated.

A base station may send (e.g., transmit) DCI and/or control signalingvia a PDCCH. The DCI may comprise a format of a plurality of formats.The DCI may comprise downlink and/or uplink scheduling information(e.g., resource allocation information, HARQ related parameters, MCS),request(s) for CSI (e.g., aperiodic CQI reports), request(s) for an SRS,uplink power control commands for one or more cells, one or more timinginformation (e.g., TB transmission/reception timing, HARQ feedbacktiming, etc.), and/or the like. The DCI may indicate an uplink grantcomprising transmission parameters for one or more transport blocks. TheDCI may indicate a downlink assignment indicating parameters forreceiving one or more transport blocks. The DCI may be used by the basestation to initiate a contention-free random access at the wirelessdevice. The base station may send (e.g., transmit) DCI comprising a slotformat indicator (SFI) indicating a slot format. The base station maysend (e.g., transmit) DCI comprising a preemption indication indicatingthe PRB(s) and/or OFDM symbol(s) in which a wireless device may assumeno transmission is intended for the wireless device. The base stationmay send (e.g., transmit) DCI for group power control of the PUCCH, thePUSCH, and/or an SRS. DCI may correspond to an RNTI. The wireless devicemay obtain an RNTI after or in response to completing the initial access(e.g., C-RNTI). The base station may configure an RNTI for the wireless(e.g., CS-RNTI, TPC-CS-RNTI, TPC-PUCCH-RNTI, TPC-PUSCH-RNTI,TPC-SRS-RNTI, etc.). The wireless device may determine (e.g., compute)an RNTI (e.g., the wireless device may determine the RA-RNTI based onresources used for transmission of a preamble). An RNTI may have apre-configured value (e.g., P-RNTI or SI-RNTI). The wireless device maymonitor a group common search space which may be used by the basestation for sending (e.g., transmitting) DCIs that are intended for agroup of wireless devices. A group common DCI may correspond to an RNTIwhich is commonly configured for a group of wireless devices. Thewireless device may monitor a wireless device-specific search space. Awireless device specific DCI may correspond to an RNTI configured forthe wireless device.

A communications system (e.g., an NR system) may support a single beamoperation and/or a multi-beam operation. In a multi-beam operation, abase station may perform a downlink beam sweeping to provide coveragefor common control channels and/or downlink SS blocks, which maycomprise at least a PSS, a SSS, and/or PBCH. A wireless device maymeasure quality of a beam pair link using one or more RSs. One or moreSS blocks, or one or more CSI-RS resources (e.g., which may beassociated with a CSI-RS resource index (CRI)), and/or one or moreDM-RSs of a PBCH, may be used as an RS for measuring a quality of a beampair link. The quality of a beam pair link may be based on a referencesignal received power (RSRP) value, a reference signal received quality(RSRQ) value, and/or a CSI value measured on RS resources. The basestation may indicate whether an RS resource, used for measuring a beampair link quality, is quasi-co-located (QCLed) with DM-RSs of a controlchannel. An RS resource and DM-RSs of a control channel may be calledQCLed, for example, if channel characteristics from a transmission on anRS to a wireless device, and that from a transmission on a controlchannel to a wireless device, are similar or the same under a configuredcriterion. In a multi-beam operation, a wireless device may perform anuplink beam sweeping to access a cell.

A wireless device may be configured to monitor a PDCCH on one or morebeam pair links simultaneously, for example, depending on a capabilityof the wireless device. This monitoring may increase robustness againstbeam pair link blocking. A base station may send (e.g., transmit) one ormore messages to configure the wireless device to monitor the PDCCH onone or more beam pair links in different PDCCH OFDM symbols. A basestation may send (e.g., transmit) higher layer signaling (e.g., RRCsignaling) and/or a MAC CE comprising parameters related to the Rx beamsetting of the wireless device for monitoring the PDCCH on one or morebeam pair links. The base station may send (e.g., transmit) anindication of a spatial QCL assumption between an DL RS antenna port(s)(e.g., a cell-specific CSI-RS, a wireless device-specific CSI-RS, an SSblock, and/or a PBCH with or without DM-RSs of the PBCH) and/or DL RSantenna port(s) for demodulation of a DL control channel. Signaling forbeam indication for a PDCCH may comprise MAC CE signaling, RRCsignaling, DCI signaling, and/or specification-transparent and/orimplicit method, and/or any combination of signaling methods.

A base station may indicate spatial QCL parameters between DL RS antennaport(s) and DM-RS antenna port(s) of a DL data channel, for example, forreception of a unicast DL data channel. The base station may send (e.g.,transmit) DCI (e.g., downlink grants) comprising information indicatingthe RS antenna port(s). The information may indicate RS antenna port(s)that may be QCLed with the DM-RS antenna port(s). A different set ofDM-RS antenna port(s) for a DL data channel may be indicated as QCL witha different set of the RS antenna port(s).

FIG. 9A shows an example of beam sweeping in a DL channel. In anRRC_INACTIVE state or RRC_IDLE state, a wireless device may assume thatSS blocks form an SS burst 940, and an SS burst set 950. The SS burstset 950 may have a given periodicity. A base station 120 may send (e.g.,transmit) SS blocks in multiple beams, together forming a SS burst 940,for example, in a multi-beam operation. One or more SS blocks may besent (e.g., transmitted) on one beam. If multiple SS bursts 940 aretransmitted with multiple beams, SS bursts together may form SS burstset 950.

A wireless device may use CSI-RS for estimating a beam quality of a linkbetween a wireless device and a base station, for example, in the multibeam operation. A beam may be associated with a CSI-RS. A wirelessdevice may (e.g., based on a RSRP measurement on CSI-RS) report a beamindex, which may be indicated in a CRI for downlink beam selectionand/or associated with an RSRP value of a beam. A CSI-RS may be sent(e.g., transmitted) on a CSI-RS resource, which may comprise at leastone of: one or more antenna ports and/or one or more time and/orfrequency radio resources. A CSI-RS resource may be configured in acell-specific way such as by common RRC signaling, or in a wirelessdevice-specific way such as by dedicated RRC signaling and/or L1/L2signaling. Multiple wireless devices covered by a cell may measure acell-specific CSI-RS resource. A dedicated subset of wireless devicescovered by a cell may measure a wireless device-specific CSI-RSresource.

A CSI-RS resource may be sent (e.g., transmitted) periodically, usingaperiodic transmission, or using a multi-shot or semi-persistenttransmission. In a periodic transmission in FIG. 9A, a base station 120may send (e.g., transmit) configured CSI-RS resources 940 periodicallyusing a configured periodicity in a time domain. In an aperiodictransmission, a configured CSI-RS resource may be sent (e.g.,transmitted) in a dedicated time slot. In a multi-shot and/orsemi-persistent transmission, a configured CSI-RS resource may be sent(e.g., transmitted) within a configured period. Beams used for CSI-RStransmission may have a different beam width than beams used forSS-blocks transmission.

FIG. 9B shows an example of a beam management procedure, such as in anexample new radio network. The base station 120 and/or the wirelessdevice 110 may perform a downlink L1/L2 beam management procedure. Oneor more of the following downlink L1/L2 beam management procedures maybe performed within one or more wireless devices 110 and one or morebase stations 120. A P1 procedure 910 may be used to enable the wirelessdevice 110 to measure one or more Transmission (Tx) beams associatedwith the base station 120, for example, to support a selection of afirst set of Tx beams associated with the base station 120 and a firstset of Rx beam(s) associated with the wireless device 110. A basestation 120 may sweep a set of different Tx beams, for example, forbeamforming at a base station 120 (such as shown in the top row, in acounter-clockwise direction). A wireless device 110 may sweep a set ofdifferent Rx beams, for example, for beamforming at a wireless device110 (such as shown in the bottom row, in a clockwise direction). A P2procedure 920 may be used to enable a wireless device 110 to measure oneor more Tx beams associated with a base station 120, for example, topossibly change a first set of Tx beams associated with a base station120. A P2 procedure 920 may be performed on a possibly smaller set ofbeams (e.g., for beam refinement) than in the P1 procedure 910. A P2procedure 920 may be a special example of a P1 procedure 910. A P3procedure 930 may be used to enable a wireless device 110 to measure atleast one Tx beam associated with a base station 120, for example, tochange a first set of Rx beams associated with a wireless device 110.

A wireless device 110 may send (e.g., transmit) one or more beammanagement reports to a base station 120. In one or more beam managementreports, a wireless device 110 may indicate one or more beam pairquality parameters comprising one or more of: a beam identification; anRSRP; a Precoding Matrix Indicator (PMI), Channel Quality Indicator(CQI), and/or Rank Indicator (RI) of a subset of configured beams. Basedon one or more beam management reports, the base station 120 may send(e.g., transmit) to a wireless device 110 a signal indicating that oneor more beam pair links are one or more serving beams. The base station120 may send (e.g., transmit) the PDCCH and the PDSCH for a wirelessdevice 110 using one or more serving beams.

A communications network (e.g., a new radio network) may support aBandwidth Adaptation (BA). Receive and/or transmit bandwidths that maybe configured for a wireless device using a BA may not be large. Receiveand/or transmit bandwidth may not be as large as a bandwidth of a cell.Receive and/or transmit bandwidths may be adjustable. A wireless devicemay change receive and/or transmit bandwidths, for example, to reduce(e.g., shrink) the bandwidth(s) at (e.g., during) a period of lowactivity such as to save power. A wireless device may change a locationof receive and/or transmit bandwidths in a frequency domain, forexample, to increase scheduling flexibility. A wireless device maychange a subcarrier spacing, for example, to allow different services.

A Bandwidth Part (BWP) may comprise a subset of a total cell bandwidthof a cell. A base station may configure a wireless device with one ormore BWPs, for example, to achieve a BA. A base station may indicate, toa wireless device, which of the one or more (configured) BWPs is anactive BWP.

FIG. 10 shows an example of BWP configurations. BWPs may be configuredas follows: BWP1 (1010 and 1050) with a width of 40 MHz and subcarrierspacing of 15 kHz; BWP2 (1020 and 1040) with a width of 10 MHz andsubcarrier spacing of 15 kHz; BWP3 1030 with a width of 20 MHz andsubcarrier spacing of 60 kHz. Any number of BWP configurations maycomprise any other width and subcarrier spacing combination.

A wireless device, configured for operation in one or more BWPs of acell, may be configured by one or more higher layers (e.g., RRC layer).The wireless device may be configured for a cell with: a set of one ormore BWPs (e.g., at most four BWPs) for reception (e.g., a DL BWP set)in a DL bandwidth by at least one parameter DL-BWP; and a set of one ormore BWPs (e.g., at most four BWPs) for transmissions (e.g., UL BWP set)in an UL bandwidth by at least one parameter UL-BWP.

A base station may configure a wireless device with one or more UL andDL BWP pairs, for example, to enable BA on the PCell. To enable BA onSCells (e.g., for CA), a base station may configure a wireless device atleast with one or more DL BWPs (e.g., there may be none in an UL).

An initial active DL BWP may comprise at least one of a location andnumber of contiguous PRBs, a subcarrier spacing, or a cyclic prefix, forexample, for a control resource set for at least one common searchspace. For operation on the PCell, one or more higher layer parametersmay indicate at least one initial UL BWP for a random access procedure.If a wireless device is configured with a secondary carrier on a primarycell, the wireless device may be configured with an initial BWP forrandom access procedure on a secondary carrier.

A wireless device may expect that a center frequency for a DL BWP may besame as a center frequency for a UL BWP, for example, for unpairedspectrum operation. A base statin may semi-statically configure awireless device for a cell with one or more parameters, for example, fora DL BWP or an UL BWP in a set of one or more DL BWPs or one or more ULBWPs, respectively. The one or more parameters may indicate one or moreof following: a subcarrier spacing; a cyclic prefix; a number ofcontiguous PRBs; an index in the set of one or more DL BWPs and/or oneor more UL BWPs; a link between a DL BWP and an UL BWP from a set ofconfigured DL BWPs and UL BWPs; DCI detection to a PDSCH receptiontiming; a PDSCH reception to a HARQ-ACK transmission timing value; DCIdetection to a PUSCH transmission timing value; and/or an offset of afirst PRB of a DL bandwidth or an UL bandwidth, respectively, relativeto a first PRB of a bandwidth.

For a DL BWP in a set of one or more DL BWPs on a PCell, a base stationmay configure a wireless device with one or more control resource setsfor at least one type of common search space and/or one wirelessdevice-specific search space. A base station may not configure awireless device without a common search space on a PCell, or on aPSCell, in an active DL BWP. For an UL BWP in a set of one or more ULBWPs, a base station may configure a wireless device with one or moreresource sets for one or more PUCCH transmissions.

DCI may comprise a BWP indicator field. The BWP indicator field valuemay indicate an active DL BWP, from a configured DL BWP set, for one ormore DL receptions. The BWP indicator field value may indicate an activeUL BWP, from a configured UL BWP set, for one or more UL transmissions.

For a PCell, a base station may semi-statically configure a wirelessdevice with a default DL BWP among configured DL BWPs. If a wirelessdevice is not provided a default DL BWP, a default BWP may be an initialactive DL BWP.

A base station may configure a wireless device with a timer value for aPCell. A wireless device may start a timer (e.g., a BWP inactivitytimer), for example, if a wireless device detects DCI indicating anactive DL BWP, other than a default DL BWP, for a paired spectrumoperation, and/or if a wireless device detects DCI indicating an activeDL BWP or UL BWP, other than a default DL BWP or UL BWP, for an unpairedspectrum operation. The wireless device may increment the timer by aninterval of a first value (e.g., the first value may be 1 millisecond,0.5 milliseconds, or any other time duration), for example, if thewireless device does not detect DCI at (e.g., during) the interval for apaired spectrum operation or for an unpaired spectrum operation. Thetimer may expire at a time that the timer is equal to the timer value. Awireless device may switch to the default DL BWP from an active DL BWP,for example, if the timer expires.

A base station may semi-statically configure a wireless device with oneor more BWPs. A wireless device may switch an active BWP from a firstBWP to a second BWP, for example, after or in response to receiving DCIindicating the second BWP as an active BWP, and/or after or in responseto an expiry of BWP inactivity timer (e.g., the second BWP may be adefault BWP). FIG. 10 shows an example of three BWPs configured, BWP1(1010 and 1050), BWP2 (1020 and 1040), and BWP3 (1030). BWP2 (1020 and1040) may be a default BWP. BWP1 (1010) may be an initial active BWP. Awireless device may switch an active BWP from BWP1 1010 to BWP2 1020,for example, after or in response to an expiry of the BWP inactivitytimer. A wireless device may switch an active BWP from BWP2 1020 to BWP31030, for example, after or in response to receiving DCI indicating BWP31030 as an active BWP. Switching an active BWP from BWP3 1030 to BWP21040 and/or from BWP2 1040 to BWP1 1050 may be after or in response toreceiving DCI indicating an active BWP, and/or after or in response toan expiry of BWP inactivity timer.

Wireless device procedures on a secondary cell may be same as on aprimary cell using the timer value for the secondary cell and thedefault DL BWP for the secondary cell, for example, if a wireless deviceis configured for a secondary cell with a default DL BWP amongconfigured DL BWPs and a timer value. A wireless device may use anindicated DL BWP and an indicated UL BWP on a secondary cell as arespective first active DL BWP and first active UL BWP on a secondarycell or carrier, for example, if a base station configures a wirelessdevice with a first active DL BWP and a first active UL BWP on asecondary cell or carrier.

FIG. 11A and FIG. 11B show packet flows using a multi connectivity(e.g., dual connectivity, multi connectivity, tight interworking, and/orthe like). FIG. 11A shows an example of a protocol structure of awireless device 110 (e.g., UE) with CA and/or multi connectivity. FIG.11B shows an example of a protocol structure of multiple base stationswith CA and/or multi connectivity. The multiple base stations maycomprise a master node, MN 1130 (e.g., a master node, a master basestation, a master gNB, a master eNB, and/or the like) and a secondarynode, SN 1150 (e.g., a secondary node, a secondary base station, asecondary gNB, a secondary eNB, and/or the like). A master node 1130 anda secondary node 1150 may co-work to communicate with a wireless device110.

If multi connectivity is configured for a wireless device 110, thewireless device 110, which may support multiple reception and/ortransmission functions in an RRC connected state, may be configured toutilize radio resources provided by multiple schedulers of a multiplebase stations. Multiple base stations may be inter-connected via anon-ideal or ideal backhaul (e.g., Xn interface, X2 interface, and/orthe like). A base station involved in multi connectivity for a certainwireless device may perform at least one of two different roles: a basestation may act as a master base station or act as a secondary basestation. In multi connectivity, a wireless device may be connected toone master base station and one or more secondary base stations. Amaster base station (e.g., the MN 1130) may provide a master cell group(MCG) comprising a primary cell and/or one or more secondary cells for awireless device (e.g., the wireless device 110). A secondary basestation (e.g., the SN 1150) may provide a secondary cell group (SCG)comprising a primary secondary cell (PSCell) and/or one or moresecondary cells for a wireless device (e.g., the wireless device 110).

In multi connectivity, a radio protocol architecture that a bearer usesmay depend on how a bearer is setup. Three different types of bearersetup options may be supported: an MCG bearer, an SCG bearer, and/or asplit bearer. A wireless device may receive and/or send (e.g., transmit)packets of an MCG bearer via one or more cells of the MCG. A wirelessdevice may receive and/or send (e.g., transmit) packets of an SCG bearervia one or more cells of an SCG. Multi-connectivity may indicate havingat least one bearer configured to use radio resources provided by thesecondary base station. Multi-connectivity may or may not be configuredand/or implemented.

A wireless device (e.g., wireless device 110) may send (e.g., transmit)and/or receive: packets of an MCG bearer via an SDAP layer (e.g., SDAP1110), a PDCP layer (e.g., NR PDCP 1111), an RLC layer (e.g., MN RLC1114), and a MAC layer (e.g., MN MAC 1118); packets of a split bearervia an SDAP layer (e.g., SDAP 1110), a PDCP layer (e.g., NR PDCP 1112),one of a master or secondary RLC layer (e.g., MN RLC 1115, SN RLC 1116),and one of a master or secondary MAC layer (e.g., MN MAC 1118, SN MAC1119); and/or packets of an SCG bearer via an SDAP layer (e.g., SDAP1110), a PDCP layer (e.g., NR PDCP 1113), an RLC layer (e.g., SN RLC1117), and a MAC layer (e.g., MN MAC 1119).

A master base station (e.g., MN 1130) and/or a secondary base station(e.g., SN 1150) may send (e.g., transmit) and/or receive: packets of anMCG bearer via a master or secondary node SDAP layer (e.g., SDAP 1120,SDAP 1140), a master or secondary node PDCP layer (e.g., NR PDCP 1121,NR PDCP 1142), a master node RLC layer (e.g., MN RLC 1124, MN RLC 1125),and a master node MAC layer (e.g., MN MAC 1128); packets of an SCGbearer via a master or secondary node SDAP layer (e.g., SDAP 1120, SDAP1140), a master or secondary node PDCP layer (e.g., NR PDCP 1122, NRPDCP 1143), a secondary node RLC layer (e.g., SN RLC 1146, SN RLC 1147),and a secondary node MAC layer (e.g., SN MAC 1148); packets of a splitbearer via a master or secondary node SDAP layer (e.g., SDAP 1120, SDAP1140), a master or secondary node PDCP layer (e.g., NR PDCP 1123, NRPDCP 1141), a master or secondary node RLC layer (e.g., MN RLC 1126, SNRLC 1144, SN RLC 1145, MN RLC 1127), and a master or secondary node MAClayer (e.g., MN MAC 1128, SN MAC 1148).

In multi connectivity, a wireless device may configure multiple MACentities, such as one MAC entity (e.g., MN MAC 1118) for a master basestation, and other MAC entities (e.g., SN MAC 1119) for a secondary basestation. In multi-connectivity, a configured set of serving cells for awireless device may comprise two subsets: an MCG comprising servingcells of a master base station, and SCGs comprising serving cells of asecondary base station. For an SCG, one or more of followingconfigurations may be used. At least one cell of an SCG may have aconfigured UL CC and at least one cell of a SCG, named as primarysecondary cell (e.g., PSCell, PCell of SCG, PCell), and may beconfigured with PUCCH resources. If an SCG is configured, there may beat least one SCG bearer or one split bearer. After or upon detection ofa physical layer problem or a random access problem on a PSCell, or anumber of NR RLC retransmissions has been reached associated with theSCG, or after or upon detection of an access problem on a PSCellassociated with (e.g., during) a SCG addition or an SCG change: an RRCconnection re-establishment procedure may not be triggered, ULtransmissions towards cells of an SCG may be stopped, a master basestation may be informed by a wireless device of a SCG failure type, a DLdata transfer over a master base station may be maintained (e.g., for asplit bearer). An NR RLC acknowledged mode (AM) bearer may be configuredfor a split bearer. A PCell and/or a PSCell may not be de-activated. APSCell may be changed with a SCG change procedure (e.g., with securitykey change and a RACH procedure). A bearer type change between a splitbearer and a SCG bearer, and/or simultaneous configuration of a SCG anda split bearer, may or may not be supported.

With respect to interactions between a master base station and asecondary base stations for multi-connectivity, one or more of thefollowing may be used. A master base station and/or a secondary basestation may maintain RRM measurement configurations of a wirelessdevice. A master base station may determine (e.g., based on receivedmeasurement reports, traffic conditions, and/or bearer types) to requesta secondary base station to provide additional resources (e.g., servingcells) for a wireless device. After or upon receiving a request from amaster base station, a secondary base station may create and/or modify acontainer that may result in a configuration of additional serving cellsfor a wireless device (or decide that the secondary base station has noresource available to do so). For a wireless device capabilitycoordination, a master base station may provide (e.g., all or a part of)an AS configuration and wireless device capabilities to a secondary basestation. A master base station and a secondary base station may exchangeinformation about a wireless device configuration such as by using RRCcontainers (e.g., inter-node messages) carried via Xn messages. Asecondary base station may initiate a reconfiguration of the secondarybase station existing serving cells (e.g., PUCCH towards the secondarybase station). A secondary base station may decide which cell is aPSCell within a SCG. A master base station may or may not change contentof RRC configurations provided by a secondary base station. A masterbase station may provide recent (and/or the latest) measurement resultsfor SCG cell(s), for example, if an SCG addition and/or an SCG SCelladdition occurs. A master base station and secondary base stations mayreceive information of SFN and/or subframe offset of each other from anOAM and/or via an Xn interface (e.g., for a purpose of DRX alignmentand/or identification of a measurement gap). Dedicated RRC signaling maybe used for sending required system information of a cell as for CA, forexample, if adding a new SCG SCell, except for an SFN acquired from anMIB of a PSCell of a SCG.

FIG. 12 shows an example of a random access procedure. One or moreevents may trigger a random access procedure. For example, one or moreevents may be at least one of following: initial access from RRC_IDLE,RRC connection re-establishment procedure, handover, DL or UL dataarrival in (e.g., during) a state of RRC_CONNECTED (e.g., if ULsynchronization status is non-synchronized), transition fromRRC_Inactive, and/or request for other system information. A PDCCHorder, a MAC entity, and/or a beam failure indication may initiate arandom access procedure.

A random access procedure may comprise or be one of at least acontention based random access procedure and/or a contention free randomaccess procedure. A contention based random access procedure maycomprise one or more Msg 1 1220 transmissions, one or more Msg2 1230transmissions, one or more Msg3 1240 transmissions, and contentionresolution 1250. A contention free random access procedure may compriseone or more Msg 1 1220 transmissions and one or more Msg2 1230transmissions. One or more of Msg 1 1220, Msg 2 1230, Msg 3 1240, and/orcontention resolution 1250 may be transmitted in the same step. Atwo-step random access procedure, for example, may comprise a firsttransmission (e.g., Msg A) and a second transmission (e.g., Msg B). Thefirst transmission (e.g., Msg A) may comprise transmitting, by awireless device (e.g., wireless device 110) to a base station (e.g.,base station 120), one or more messages indicating an equivalent and/orsimilar contents of Msg1 1220 and Msg3 1240 of a four-step random accessprocedure. The second transmission (e.g., Msg B) may comprisetransmitting, by the base station (e.g., base station 120) to a wirelessdevice (e.g., wireless device 110) after or in response to the firstmessage, one or more messages indicating an equivalent and/or similarcontent of Msg2 1230 and contention resolution 1250 of a four-steprandom access procedure.

A base station may send (e.g., transmit, unicast, multicast, broadcast,etc.), to a wireless device, a RACH configuration 1210 via one or morebeams. The RACH configuration 1210 may comprise one or more parametersindicating at least one of following: an available set of PRACHresources for a transmission of a random access preamble, initialpreamble power (e.g., random access preamble initial received targetpower), an RSRP threshold for a selection of a SS block andcorresponding PRACH resource, a power-ramping factor (e.g., randomaccess preamble power ramping step), a random access preamble index, amaximum number of preamble transmissions, preamble group A and group B,a threshold (e.g., message size) to determine the groups of randomaccess preambles, a set of one or more random access preambles for asystem information request and corresponding PRACH resource(s) (e.g., ifany), a set of one or more random access preambles for a beam failurerecovery (BFR) procedure and corresponding PRACH resource(s) (e.g., ifany), a time window to monitor RA response(s), a time window to monitorresponse(s) on a BFR procedure, and/or a contention resolution timer.

The Msg1 1220 may comprise one or more transmissions of a random accesspreamble. For a contention based random access procedure, a wirelessdevice may select an SS block with an RSRP above the RSRP threshold. Ifrandom access preambles group B exists, a wireless device may select oneor more random access preambles from a group A or a group B, forexample, depending on a potential Msg3 1240 size. If a random accesspreambles group B does not exist, a wireless device may select the oneor more random access preambles from a group A. A wireless device mayselect a random access preamble index randomly (e.g., with equalprobability or a normal distribution) from one or more random accesspreambles associated with a selected group. If a base stationsemi-statically configures a wireless device with an association betweenrandom access preambles and SS blocks, the wireless device may select arandom access preamble index randomly with equal probability from one ormore random access preambles associated with a selected SS block and aselected group.

A wireless device may initiate a contention free random accessprocedure, for example, based on a beam failure indication from a lowerlayer. A base station may semi-statically configure a wireless devicewith one or more contention free PRACH resources for a BFR procedureassociated with at least one of SS blocks and/or CSI-RSs. A wirelessdevice may select a random access preamble index corresponding to aselected SS block or a CSI-RS from a set of one or more random accesspreambles for a BFR procedure, for example, if at least one of the SSblocks with an RSRP above a first RSRP threshold amongst associated SSblocks is available, and/or if at least one of CSI-RSs with a RSRP abovea second RSRP threshold amongst associated CSI-RSs is available.

A wireless device may receive, from a base station, a random accesspreamble index via PDCCH or RRC for a contention free random accessprocedure. The wireless device may select a random access preambleindex, for example, if a base station does not configure a wirelessdevice with at least one contention free PRACH resource associated withSS blocks or CSI-RS. The wireless device may select the at least one SSblock and/or select a random access preamble corresponding to the atleast one SS block, for example, if a base station configures thewireless device with one or more contention free PRACH resourcesassociated with SS blocks and/or if at least one SS block with a RSRPabove a first RSRP threshold amongst associated SS blocks is available.The wireless device may select the at least one CSI-RS and/or select arandom access preamble corresponding to the at least one CSI-RS, forexample, if a base station configures a wireless device with one or morecontention free PRACH resources associated with CSI-RSs and/or if atleast one CSI-RS with a RSRP above a second RSPR threshold amongst theassociated CSI-RSs is available.

A wireless device may perform one or more Msg1 1220 transmissions, forexample, by sending (e.g., transmitting) the selected random accesspreamble. The wireless device may determine a PRACH occasion from one ormore PRACH occasions corresponding to a selected SS block, for example,if the wireless device selects an SS block and is configured with anassociation between one or more PRACH occasions and/or one or more SSblocks. The wireless device may determine a PRACH occasion from one ormore PRACH occasions corresponding to a selected CSI-RS, for example, ifthe wireless device selects a CSI-RS and is configured with anassociation between one or more PRACH occasions and one or more CSI-RSs.The wireless device may send (e.g., transmit), to a base station, aselected random access preamble via a selected PRACH occasions. Thewireless device may determine a transmit power for a transmission of aselected random access preamble at least based on an initial preamblepower and a power-ramping factor. The wireless device may determine anRA-RNTI associated with a selected PRACH occasion in which a selectedrandom access preamble is sent (e.g., transmitted). The wireless devicemay not determine an RA-RNTI for a BFR procedure. The wireless devicemay determine an RA-RNTI at least based on an index of a first OFDMsymbol, an index of a first slot of a selected PRACH occasions, and/oran uplink carrier index for a transmission of Msg1 1220.

A wireless device may receive, from a base station, a random accessresponse, Msg 2 1230. The wireless device may start a time window (e.g.,ra-ResponseWindow) to monitor a random access response. For a BFRprocedure, the base station may configure the wireless device with adifferent time window (e.g., bfr-ResponseWindow) to monitor response ona BFR procedure. The wireless device may start a time window (e.g.,ra-ResponseWindow or bfr-ResponseWindow) at a start of a first PDCCHoccasion, for example, after a fixed duration of one or more symbolsfrom an end of a preamble transmission. If the wireless device sends(e.g., transmits) multiple preambles, the wireless device may start atime window at a start of a first PDCCH occasion after a fixed durationof one or more symbols from an end of a first preamble transmission. Thewireless device may monitor a PDCCH of a cell for at least one randomaccess response identified by a RA-RNTI, or for at least one response toa BFR procedure identified by a C-RNTI, at a time that a timer for atime window is running.

A wireless device may determine that a reception of random accessresponse is successful, for example, if at least one random accessresponse comprises a random access preamble identifier corresponding toa random access preamble sent (e.g., transmitted) by the wirelessdevice. The wireless device may determine that the contention freerandom access procedure is successfully completed, for example, if areception of a random access response is successful. The wireless devicemay determine that a contention free random access procedure issuccessfully complete, for example, if a contention free random accessprocedure is triggered for a BFR procedure and if a PDCCH transmissionis addressed to a C-RNTI. The wireless device may determine that therandom access procedure is successfully completed, and may indicate areception of an acknowledgement for a system information request toupper layers, for example, if at least one random access responsecomprises a random access preamble identifier. The wireless device maystop sending (e.g., transmitting) remaining preambles (if any) after orin response to a successful reception of a corresponding random accessresponse, for example, if the wireless device has signaled multiplepreamble transmissions.

The wireless device may perform one or more Msg 3 1240 transmissions,for example, after or in response to a successful reception of randomaccess response (e.g., for a contention based random access procedure).The wireless device may adjust an uplink transmission timing, forexample, based on a timing advanced command indicated by a random accessresponse. The wireless device may send (e.g., transmit) one or moretransport blocks, for example, based on an uplink grant indicated by arandom access response. Subcarrier spacing for PUSCH transmission forMsg3 1240 may be provided by at least one higher layer (e.g., RRC)parameter. The wireless device may send (e.g., transmit) a random accesspreamble via a PRACH, and Msg3 1240 via PUSCH, on the same cell. A basestation may indicate an UL BWP for a PUSCH transmission of Msg3 1240 viasystem information block. The wireless device may use HARQ for aretransmission of Msg 3 1240.

Multiple wireless devices may perform Msg 1 1220, for example, bysending (e.g., transmitting) the same preamble to a base station. Themultiple wireless devices may receive, from the base station, the samerandom access response comprising an identity (e.g., TC-RNTI).Contention resolution (e.g., comprising the wireless device 110receiving contention resolution 1250) may be used to increase thelikelihood that a wireless device does not incorrectly use an identityof another wireless device. The contention resolution 1250 may be basedon, for example, a C-RNTI on a PDCCH, and/or a wireless devicecontention resolution identity on a DL-SCH. If a base station assigns aC-RNTI to a wireless device, the wireless device may perform contentionresolution (e.g., comprising receiving contention resolution 1250), forexample, based on a reception of a PDCCH transmission that is addressedto the C-RNTI. The wireless device may determine that contentionresolution is successful, and/or that a random access procedure issuccessfully completed, for example, after or in response to detecting aC-RNTI on a PDCCH. If a wireless device has no valid C-RNTI, acontention resolution may be addressed by using a TC-RNTI. If a MAC PDUis successfully decoded and a MAC PDU comprises a wireless devicecontention resolution identity MAC CE that matches or otherwisecorresponds with the CCCH SDU sent (e.g., transmitted) in Msg3 1250, thewireless device may determine that the contention resolution (e.g.,comprising contention resolution 1250) is successful and/or the wirelessdevice may determine that the random access procedure is successfullycompleted.

FIG. 13 shows an example structure for MAC entities. A wireless devicemay be configured to operate in a multi-connectivity mode. A wirelessdevice in RRC_CONNECTED with multiple Rx/Tx may be configured to utilizeradio resources provided by multiple schedulers that may be located in aplurality of base stations. The plurality of base stations may beconnected via a non-ideal or ideal backhaul over the Xn interface. Abase station in a plurality of base stations may act as a master basestation or as a secondary base station. A wireless device may beconnected to and/or in communication with, for example, one master basestation and one or more secondary base stations. A wireless device maybe configured with multiple MAC entities, for example, one MAC entityfor a master base station, and one or more other MAC entities forsecondary base station(s). A configured set of serving cells for awireless device may comprise two subsets: an MCG comprising servingcells of a master base station, and one or more SCGs comprising servingcells of a secondary base station(s). FIG. 13 shows an example structurefor MAC entities in which a MCG and a SCG are configured for a wirelessdevice.

At least one cell in a SCG may have a configured UL CC. A cell of the atleast one cell may comprise a PSCell or a PCell of a SCG, or a PCell. APSCell may be configured with PUCCH resources. There may be at least oneSCG bearer, or one split bearer, for a SCG that is configured. After orupon detection of a physical layer problem or a random access problem ona PSCell, after or upon reaching a number of RLC retransmissionsassociated with the SCG, and/or after or upon detection of an accessproblem on a PSCell associated with (e.g., during) a SCG addition or aSCG change: an RRC connection re-establishment procedure may not betriggered, UL transmissions towards cells of a SCG may be stopped,and/or a master base station may be informed by a wireless device of aSCG failure type and DL data transfer over a master base station may bemaintained.

A MAC sublayer may provide services such as data transfer and radioresource allocation to upper layers (e.g., 1310 or 1320). A MAC sublayermay comprise a plurality of MAC entities (e.g., 1350 and 1360). A MACsublayer may provide data transfer services on logical channels. Toaccommodate different kinds of data transfer services, multiple types oflogical channels may be defined. A logical channel may support transferof a particular type of information. A logical channel type may bedefined by what type of information (e.g., control or data) istransferred. BCCH, PCCH, CCCH and/or DCCH may be control channels, andDTCH may be a traffic channel. A first MAC entity (e.g., 1310) mayprovide services on PCCH, BCCH, CCCH, DCCH, DTCH, and/or MAC controlelements. A second MAC entity (e.g., 1320) may provide services on BCCH,DCCH, DTCH, and/or MAC control elements.

A MAC sublayer may expect from a physical layer (e.g., 1330 or 1340)services such as data transfer services, signaling of HARQ feedback,and/or signaling of scheduling request or measurements (e.g., CQI). Indual connectivity, two MAC entities may be configured for a wirelessdevice: one for a MCG and one for a SCG. A MAC entity of a wirelessdevice may handle a plurality of transport channels. A first MAC entitymay handle first transport channels comprising a PCCH of a MCG, a firstBCH of the MCG, one or more first DL-SCHs of the MCG, one or more firstUL-SCHs of the MCG, and/or one or more first RACHs of the MCG. A secondMAC entity may handle second transport channels comprising a second BCHof a SCG, one or more second DL-SCHs of the SCG, one or more secondUL-SCHs of the SCG, and/or one or more second RACHs of the SCG.

If a MAC entity is configured with one or more SCells, there may bemultiple DL-SCHs, multiple UL-SCHs, and/or multiple RACHs per MACentity. There may be one DL-SCH and/or one UL-SCH on an SpCell. Theremay be one DL-SCH, zero or one UL-SCH, and/or zero or one RACH for anSCell. A DL-SCH may support receptions using different numerologiesand/or TTI duration within a MAC entity. A UL-SCH may supporttransmissions using different numerologies and/or TTI duration withinthe MAC entity.

A MAC sublayer may support different functions. The MAC sublayer maycontrol these functions with a control (e.g., Control 1355 and/orControl 1365) element. Functions performed by a MAC entity may compriseone or more of: mapping between logical channels and transport channels(e.g., in uplink or downlink), multiplexing (e.g., (De-) Multiplexing1352 and/or (De-) Multiplexing 1362) of MAC SDUs from one or differentlogical channels onto transport blocks (TBs) to be delivered to thephysical layer on transport channels (e.g., in uplink), demultiplexing(e.g., (De-) Multiplexing 1352 and/or (De-) Multiplexing 1362) of MACSDUs to one or different logical channels from transport blocks (TBs)delivered from the physical layer on transport channels (e.g., indownlink), scheduling information reporting (e.g., in uplink), errorcorrection through HARQ in uplink and/or downlink (e.g., 1363), andlogical channel prioritization in uplink (e.g., Logical ChannelPrioritization 1351 and/or Logical Channel Prioritization 1361). A MACentity may handle a random access process (e.g., Random Access Control1354 and/or Random Access Control 1364).

FIG. 14 shows an example of a RAN architecture comprising one or morebase stations. A protocol stack (e.g., RRC, SDAP, PDCP, RLC, MAC, and/orPHY) may be supported at a node. A base station (e.g., gNB 120A and/or120B) may comprise a base station central unit (CU) (e.g., gNB-CU 1420Aor 1420B) and at least one base station distributed unit (DU) (e.g.,gNB-DU 1430A, 1430B, 1430C, and/or 1430D), for example, if a functionalsplit is configured. Upper protocol layers of a base station may belocated in a base station CU, and lower layers of the base station maybe located in the base station DUs. An F1 interface (e.g., CU-DUinterface) connecting a base station CU and base station DUs may be anideal or non-ideal backhaul. F1-C may provide a control plane connectionover an F1 interface, and F1-U may provide a user plane connection overthe F1 interface. An Xn interface may be configured between base stationCUs.

A base station CU may comprise an RRC function, an SDAP layer, and/or aPDCP layer. Base station DUs may comprise an RLC layer, a MAC layer,and/or a PHY layer. Various functional split options between a basestation CU and base station DUs may be possible, for example, bylocating different combinations of upper protocol layers (e.g., RANfunctions) in a base station CU and different combinations of lowerprotocol layers (e.g., RAN functions) in base station DUs. A functionalsplit may support flexibility to move protocol layers between a basestation CU and base station DUs, for example, depending on servicerequirements and/or network environments.

Functional split options may be configured per base station, per basestation CU, per base station DU, per wireless device, per bearer, perslice, and/or with other granularities. In a per base station CU split,a base station CU may have a fixed split option, and base station DUsmay be configured to match a split option of a base station CU. In a perbase station DU split, a base station DU may be configured with adifferent split option, and a base station CU may provide differentsplit options for different base station DUs. In a per wireless devicesplit, a base station (e.g., a base station CU and at least one basestation DUs) may provide different split options for different wirelessdevices. In a per bearer split, different split options may be utilizedfor different bearers. In a per slice splice, different split optionsmay be used for different slices.

FIG. 15 shows example RRC state transitions of a wireless device. Awireless device may be in at least one RRC state among an RRC connectedstate (e.g., RRC Connected 1530, RRC_Connected, etc.), an RRC idle state(e.g., RRC Idle 1510, RRC_Idle, etc.), and/or an RRC inactive state(e.g., RRC Inactive 1520, RRC_Inactive, etc.). In an RRC connectedstate, a wireless device may have at least one RRC connection with atleast one base station (e.g., gNB and/or eNB), which may have a contextof the wireless device (e.g., UE context). A wireless device context(e.g., UE context) may comprise at least one of an access stratumcontext, one or more radio link configuration parameters, bearer (e.g.,data radio bearer (DRB), signaling radio bearer (SRB), logical channel,QoS flow, PDU session, and/or the like) configuration information,security information, PHY/MAC/RLC/PDCP/SDAP layer configurationinformation, and/or the like configuration information for a wirelessdevice. In an RRC idle state, a wireless device may not have an RRCconnection with a base station, and a context of the wireless device maynot be stored in a base station. In an RRC inactive state, a wirelessdevice may not have an RRC connection with a base station. A context ofa wireless device may be stored in a base station, which may comprise ananchor base station (e.g., a last serving base station).

A wireless device may transition an RRC state (e.g., UE RRC state)between an RRC idle state and an RRC connected state in both ways (e.g.,connection release 1540 or connection establishment 1550; and/orconnection reestablishment) and/or between an RRC inactive state and anRRC connected state in both ways (e.g., connection inactivation 1570 orconnection resume 1580). A wireless device may transition its RRC statefrom an RRC inactive state to an RRC idle state (e.g., connectionrelease 1560).

An anchor base station may be a base station that may keep a context ofa wireless device (e.g., UE context) at least at (e.g., during) a timeperiod that the wireless device stays in a RAN notification area (RNA)of an anchor base station, and/or at (e.g., during) a time period thatthe wireless device stays in an RRC inactive state. An anchor basestation may comprise a base station that a wireless device in an RRCinactive state was most recently connected to in a latest RRC connectedstate, and/or a base station in which a wireless device most recentlyperformed an RNA update procedure. An RNA may comprise one or more cellsoperated by one or more base stations. A base station may belong to oneor more RNAs. A cell may belong to one or more RNAs.

A wireless device may transition, in a base station, an RRC state (e.g.,UE RRC state) from an RRC connected state to an RRC inactive state. Thewireless device may receive RNA information from the base station. RNAinformation may comprise at least one of an RNA identifier, one or morecell identifiers of one or more cells of an RNA, a base stationidentifier, an IP address of the base station, an AS context identifierof the wireless device, a resume identifier, and/or the like.

An anchor base station may broadcast a message (e.g., RAN pagingmessage) to base stations of an RNA to reach to a wireless device in anRRC inactive state. The base stations receiving the message from theanchor base station may broadcast and/or multicast another message(e.g., paging message) to wireless devices in their coverage area, cellcoverage area, and/or beam coverage area associated with the RNA via anair interface.

A wireless device may perform an RNA update (RNAU) procedure, forexample, if the wireless device is in an RRC inactive state and movesinto a new RNA. The RNAU procedure may comprise a random accessprocedure by the wireless device and/or a context retrieve procedure(e.g., UE context retrieve). A context retrieve procedure may comprise:receiving, by a base station from a wireless device, a random accesspreamble; and requesting and/or receiving (e.g., fetching), by a basestation, a context of the wireless device (e.g., UE context) from an oldanchor base station. The requesting and/or receiving (e.g., fetching)may comprise: sending a retrieve context request message (e.g., UEcontext request message) comprising a resume identifier to the oldanchor base station and receiving a retrieve context response messagecomprising the context of the wireless device from the old anchor basestation.

A wireless device in an RRC inactive state may select a cell to camp onbased on at least a measurement result for one or more cells, a cell inwhich a wireless device may monitor an RNA paging message, and/or a corenetwork paging message from a base station. A wireless device in an RRCinactive state may select a cell to perform a random access procedure toresume an RRC connection and/or to send (e.g., transmit) one or morepackets to a base station (e.g., to a network). The wireless device mayinitiate a random access procedure to perform an RNA update procedure,for example, if a cell selected belongs to a different RNA from an RNAfor the wireless device in an RRC inactive state. The wireless devicemay initiate a random access procedure to send (e.g., transmit) one ormore packets to a base station of a cell that the wireless deviceselects, for example, if the wireless device is in an RRC inactive stateand has one or more packets (e.g., in a buffer) to send (e.g., transmit)to a network. A random access procedure may be performed with twomessages (e.g., 2-stage or 2-step random access) and/or four messages(e.g., 4-stage or 4-step random access) between the wireless device andthe base station.

A base station receiving one or more uplink packets from a wirelessdevice in an RRC inactive state may request and/or receive (e.g., fetch)a context of a wireless device (e.g., UE context), for example, bysending (e.g., transmitting) a retrieve context request message for thewireless device to an anchor base station of the wireless device basedon at least one of an AS context identifier, an RNA identifier, a basestation identifier, a resume identifier, and/or a cell identifierreceived from the wireless device. A base station may send (e.g.,transmit) a path switch request for a wireless device to a core networkentity (e.g., AMF, MME, and/or the like), for example, after or inresponse to requesting and/or receiving (e.g., fetching) a context. Acore network entity may update a downlink tunnel endpoint identifier forone or more bearers established for the wireless device between a userplane core network entity (e.g., UPF, S-GW, and/or the like) and a RANnode (e.g., the base station), such as by changing a downlink tunnelendpoint identifier from an address of the anchor base station to anaddress of the base station).

A base station may send (e.g., transmit) one or more MAC PDUs to awireless device. A MAC PDU may comprise a bit string that may be bytealigned (e.g., multiple of eight bits) in length. Bit strings may berepresented by tables in which the most significant bit is the leftmostbit of the first line of the table, and the least significant bit is therightmost bit on the last line of the table. The bit string may be readfrom the left to right, and then, in the reading order of the lines. Thebit order of a parameter field within a MAC PDU may be represented withthe first and most significant bit in the leftmost bit, and with thelast and least significant bit in the rightmost bit.

A MAC SDU may comprise a bit string that is byte aligned (e.g., multipleof eight bits) in length. A MAC SDU may be included in a MAC PDU, forexample, from the first bit onward. In an example, a MAC CE may be a bitstring that is byte aligned (e.g., multiple of eight bits) in length. AMAC subheader may be a bit string that is byte aligned (e.g., multipleof eight bits) in length. A MAC subheader may be placed immediately infront of the corresponding MAC SDU, MAC CE, and/or padding. A MAC entitymay ignore a value of reserved bits in a DL MAC PDU.

A MAC PDU may comprise one or more MAC subPDUs. A MAC subPDU of the oneor more MAC subPDUs may comprise at least one of: a MAC subheader only(e.g., including padding); a MAC subheader and a MAC SDU; a MACsubheader and a MAC CE; and/or a MAC subheader and padding. The MAC SDUmay be of variable size. A MAC subheader may correspond to a MAC SDU, aMAC CE, and/or padding.

A MAC subheader may comprise: an R field comprising one bit; an F fieldwith one bit in length; an LCID field with multiple bits in length; an Lfield with multiple bits in length, for example, if the MAC subheadercorresponds to a MAC SDU, a variable-sized MAC CE, and/or padding.

FIG. 16A shows an example of a MAC subheader comprising an eight-bit Lfield. The LCID field may have six bits in length. The L field may haveeight bits in length.

FIG. 16B shows an example of a MAC subheader with a sixteen-bit L field.The LCID field may have six bits in length. The L field may have sixteenbits in length. A MAC subheader may comprise: a R field comprising twobits in length; and an LCID field comprising multiple bits in length(e.g., if the MAC subheader corresponds to a fixed sized MAC CE), and/orpadding.

FIG. 16C shows an example of the MAC subheader. The LCID field maycomprise six bits in length, and the R field may comprise two bits inlength.

FIG. 17A shows an example of a DL MAC PDU. Multiple MAC CEs may beplaced together. A MAC subPDU comprising MAC CE may be placed before anyMAC subPDU comprising a MAC SDU, and/or before a MAC subPDU comprisingpadding.

FIG. 17B shows an example of a UL MAC PDU. Multiple MAC CEs may beplaced together. A MAC subPDU comprising a MAC CE may be placed afterall MAC subPDU comprising a MAC SDU. The MAC subPDU may be placed beforea MAC subPDU comprising padding.

FIG. 18A shows examples of multiple LCIDs associated with the one ormore MAC CEs. A MAC entity of a base station may send (e.g., transmit)to a MAC entity of a wireless device one or more MAC CEs. The one ormore MAC CEs may comprise at least one of: a wireless device (e.g., UE)contention resolution identity MAC CE; a timing advance command MAC CE;a DRX command MAC CE; a long DRX command MAC CE; an SCell activationand/or deactivation MAC CE (e.g., 1 Octet); an SCell activation and/ordeactivation MAC CE (e.g., 4 Octet); and/or a duplication activationand/or deactivation MAC CE. A MAC CE may comprise an LCID in thecorresponding MAC subheader. Different MAC CEs may have different LCIDin the corresponding MAC subheader. An LCID with 111011 in a MACsubheader may indicate a MAC CE associated with the MAC subheader is along DRX command MAC CE.

FIG. 18B shows further examples of LCIDs associated with one or more MACCEs. The MAC entity of the wireless device may send (e.g., transmit), tothe MAC entity of the base station, one or more MAC CEs. The one or moreMAC CEs may comprise at least one of: a short buffer status report (BSR)MAC CE; a long BSR MAC CE; a C-RNTI MAC CE; a configured grantconfirmation MAC CE; a single entry power headroom report (PHR) MAC CE;a multiple entry PHR MAC CE; a short truncated BSR; and/or a longtruncated BSR. A MAC CE may comprise an LCID in the corresponding MACsubheader. Different MAC CEs may have different LCIDs in thecorresponding MAC subheader. The LCID with 111011 in a MAC subheader mayindicate a MAC CE associated with the MAC subheader is a short-truncatedcommand MAC CE.

Two or more component carriers (CCs) may be aggregated, for example, ina carrier aggregation (CA). A wireless device may simultaneously receiveand/or transmit on one or more CCs, for example, depending oncapabilities of the wireless device. The CA may be supported forcontiguous CCs. The CA may be supported for non-contiguous CCs.

A wireless device may have one RRC connection with a network, forexample, if configured with CA. At (e.g., during) an RRC connectionestablishment, re-establishment and/or handover, a cell providing a NASmobility information may be a serving cell. At (e.g., during) an RRCconnection re-establishment and/or handover procedure, a cell providinga security input may be a serving cell. The serving cell may be referredto as a primary cell (PCell). A base station may send (e.g., transmit),to a wireless device, one or more messages comprising configurationparameters of a plurality of one or more secondary cells (SCells), forexample, depending on capabilities of the wireless device.

A base station and/or a wireless device may use an activation and/ordeactivation mechanism of an SCell for an efficient battery consumption,for example, if the base station and/or the wireless device isconfigured with CA. A base station may activate or deactivate at leastone of the one or more SCells, for example, if the wireless device isconfigured with one or more SCells. The SCell may be deactivated, forexample, after or upon configuration of an SCell.

A wireless device may activate and/or deactivate an SCell, for example,after or in response to receiving an SCell activation and/ordeactivation MAC CE. A base station may send (e.g., transmit), to awireless device, one or more messages comprising ansCellDeactivationTimer timer. The wireless device may deactivate anSCell, for example, after or in response to an expiry of thesCellDeactivationTimer timer.

A wireless device may activate an SCell, for example, if the wirelessdevice receives an SCell activation/deactivation MAC CE activating anSCell. The wireless device may perform operations (e.g., after or inresponse to the activating the SCell) that may comprise: SRStransmissions on the SCell; CQI, PMI, RI, and/or CRI reporting for theSCell on a PCell; PDCCH monitoring on the SCell; PDCCH monitoring forthe SCell on the PCell; and/or PUCCH transmissions on the SCell.

The wireless device may start and/or restart a timer (e.g., ansCellDeactivationTimer timer) associated with the SCell, for example,after or in response to activating the SCell. The wireless device maystart the timer (e.g., sCellDeactivationTimer timer) in the slot, forexample, if the SCell activation/deactivation MAC CE has been received.The wireless device may initialize and/or re-initialize one or moresuspended configured uplink grants of a configured grant Type 1associated with the SCell according to a stored configuration, forexample, after or in response to activating the SCell. The wirelessdevice may trigger a PHR, for example, after or in response toactivating the SCell.

The wireless device may deactivate the activated SCell, for example, ifthe wireless device receives an SCell activation/deactivation MAC CEdeactivating an activated SCell. The wireless device may deactivate theactivated SCell, for example, if a timer (e.g., ansCellDeactivationTimer timer) associated with an activated SCellexpires. The wireless device may stop the timer (e.g.,sCellDeactivationTimer timer) associated with the activated SCell, forexample, after or in response to deactivating the activated SCell. Thewireless device may clear one or more configured downlink assignmentsand/or one or more configured uplink grant Type 2 associated with theactivated SCell, for example, after or in response to the deactivatingthe activated SCell. The wireless device may suspend one or moreconfigured uplink grant Type 1 associated with the activated SCell, forexample, after or in response to deactivating the activated SCell. Thewireless device may flush HARQ buffers associated with the activatedSCell.

A wireless device may not perform certain operations, for example, if anSCell is deactivated. The wireless device may not perform one or more ofthe following operations if an SCell is deactivated: transmitting SRS onthe SCell; reporting CQI, PMI, RI, and/or CRI for the SCell on a PCell;transmitting on UL-SCH on the SCell; transmitting on a RACH on theSCell; monitoring at least one first PDCCH on the SCell; monitoring atleast one second PDCCH for the SCell on the PCell; and/or transmitting aPUCCH on the SCell.

A wireless device may restart a timer (e.g., an sCellDeactivationTimertimer) associated with the activated SCell, for example, if at least onefirst PDCCH on an activated S Cell indicates an uplink grant or adownlink assignment. A wireless device may restart a timer (e.g., ansCellDeactivationTimer timer) associated with the activated SCell, forexample, if at least one second PDCCH on a serving cell (e.g. a PCell oran SCell configured with PUCCH, such as a PUCCH SCell) scheduling theactivated SCell indicates an uplink grant and/or a downlink assignmentfor the activated SCell. A wireless device may abort the ongoing randomaccess procedure on the SCell, for example, if an SCell is deactivatedand/or if there is an ongoing random access procedure on the SCell.

FIG. 18A shows first examples of LCIDs. FIG. 18B shows second examplesof LCIDs. The left columns comprise indices. The right columns comprisescorresponding LCID values for each index.

FIG. 19A shows an example of an SCell activation/deactivation MAC CE ofone octet. A first MAC PDU subheader comprising a first LCID mayidentify the SCell activation/deactivation MAC CE of one octet. An SCellactivation/deactivation MAC CE of one octet may have a fixed size. TheSCell activation/deactivation MAC CE of one octet may comprise a singleoctet. The single octet may comprise a first number of C-fields (e.g.,seven) and a second number of R-fields (e.g., one).

FIG. 19B shows an example of an SCell Activation/Deactivation MAC CE offour octets. A second MAC PDU subheader with a second LCID may identifythe SCell Activation/Deactivation MAC CE of four octets. An SCellactivation/deactivation MAC CE of four octets may have a fixed size. TheSCell activation/deactivation MAC CE of four octets may comprise fouroctets. The four octets may comprise a third number of C-fields (e.g.,31) and a fourth number of R-fields (e.g., 1). A C_i field may indicatean activation/deactivation status of an SCell with an SCell index i. AnSCell with an SCell index i may be activated, for example, if the C_ifield is set to one. An SCell with an SCell index i may be deactivated,for example, In an example, if the C_i field is set to zero. An R fieldmay indicate a reserved bit. The R field may be set to zero.

A base station may send (e.g., transmit) DCI via a PDCCH for at leastone of: a scheduling assignment and/or grant; a slot formatnotification; a pre-emption indication; and/or a power-control command.The DCI may comprise at least one of: an identifier of a DCI format; adownlink scheduling assignment(s); an uplink scheduling grant(s); a slotformat indicator; a pre-emption indication; a power-control forPUCCH/PUSCH; and/or a power-control for SRS.

A downlink scheduling assignment DCI may comprise parameters indicatingat least one of: an identifier of a DCI format; a PDSCH resourceindication; a transport format; HARQ information; control informationrelated to multiple antenna schemes; and/or a command for power controlof the PUCCH. An uplink scheduling grant DCI may comprise parametersindicating at least one of: an identifier of a DCI format; a PUSCHresource indication; a transport format; HARQ related information;and/or a power control command of the PUSCH.

Different types of control information may correspond to different DCImessage sizes. Supporting multiple beams, spatial multiplexing in thespatial domain, and/or noncontiguous allocation of RB s in the frequencydomain, may require a larger scheduling message, in comparison with anuplink grant allowing for frequency-contiguous allocation. DCI may becategorized into different DCI formats. A DCI format may correspond to acertain message size and/or usage.

A wireless device may monitor (e.g., in common search space or wirelessdevice-specific search space) one or more PDCCH for detecting one ormore DCI with one or more DCI format. A wireless device may monitor aPDCCH with a limited set of DCI formats, for example, which may reducepower consumption. The more DCI formats that are to be detected, themore power may be consumed by the wireless device.

The information in the DCI formats for downlink scheduling may compriseat least one of: an identifier of a DCI format; a carrier indicator; anRB allocation; a time resource allocation; a bandwidth part indicator; aHARQ process number; one or more MCS; one or more NDI; one or more RV;MIMO related information; a downlink assignment index (DAI); a TPC forPUCCH; an SRS request; and/or padding (e.g., if necessary). The MIMOrelated information may comprise at least one of: a PMI; precodinginformation; a transport block swap flag; a power offset between PDSCHand a reference signal; a reference-signal scrambling sequence; a numberof layers; antenna ports for the transmission; and/or a transmissionconfiguration indication (TCI).

The information in the DCI formats used for uplink scheduling maycomprise at least one of: an identifier of a DCI format; a carrierindicator; a bandwidth part indication; a resource allocation type; anRB allocation; a time resource allocation; an MCS; an NDI; a phaserotation of the uplink DMRS; precoding information; a CSI request; anSRS request; an uplink index/DAI; a TPC for PUSCH; and/or padding (e.g.,if necessary).

A base station may perform cyclic redundancy check (CRC) scrambling fora DCI, for example, before transmitting the DCI via a PDCCH. The basestation may perform CRC scrambling by binarily adding multiple bits ofat least one wireless device identifier (e.g., C-RNTI, CS-RNTI,TPC-CS-RNTI, TPC-PUCCH-RNTI, TPC-PUSCH-RNTI, SP CSI C-RNTI, and/orTPC-SRS-RNTI) on the CRC bits of the DCI. The wireless device may checkthe CRC bits of the DCI, for example, if detecting the DCI. The wirelessdevice may receive the DCI, for example, if the CRC is scrambled by asequence of bits that is the same as the at least one wireless deviceidentifier.

A base station may send (e.g., transmit) one or more PDCCH in differentCORESETs, for example, to support a wide bandwidth operation. A basestation may transmit one or more RRC messages comprising configurationparameters of one or more CORESETs. A CORESET may comprise at least oneof: a first OFDM symbol; a number of consecutive OFDM symbols; a set ofresource blocks; and/or a control channel element (CCE) to resourceelement group (REG) (CCE-to-REG) mapping. A base station may send (e.g.,transmit) a PDCCH in a dedicated CORESET for particular purpose, forexample, for beam failure recovery confirmation. A wireless device maymonitor a PDCCH for detecting DCI in one or more configured CORESETs,for example, to reduce the power consumption.

A base station and/or a wireless device may have multiple antennas, forexample, to support a transmission with high data rate (such as in an NRsystem). A wireless device may perform one or more beam managementprocedures, as shown in FIG. 9B, for example, if configured withmultiple antennas.

A wireless device may perform a downlink beam management based on one ormore CSI-RSs and/or one or more SS blocks. In a beam managementprocedure, a wireless device may measure a channel quality of a beampair link. The beam pair link may comprise a transmitting beam from abase station and a receiving beam at the wireless device. A wirelessdevice may measure the multiple beam pair links between the base stationand the wireless device, for example, if the wireless device isconfigured with multiple beams associated with multiple CSI-RSs and/orSS blocks.

A wireless device may send (e.g., transmit) one or more beam managementreports to a base station. The wireless device may indicate one or morebeam pair quality parameters, for example, in a beam management report.The one or more beam pair quality parameters may comprise at least oneor more beam identifications; RSRP; and/or PMI, CQI, and/or RI of atleast a subset of configured multiple beams.

A base station and/or a wireless device may perform a downlink beammanagement procedure on one or multiple Transmission and Receiving Point(TRPs), such as shown in FIG. 9B. Based on a wireless device's beammanagement report, a base station may send (e.g., transmit), to thewireless device, a signal indicating that a new beam pair link is aserving beam. The base station may transmit PDCCH and/or PDSCH to thewireless device using the serving beam.

A wireless device and/or a base station may trigger a beam failurerecovery mechanism. A wireless device may trigger a beam failurerecovery request (BFRQ) procedure, for example, if at least a beamfailure occurs. A beam failure may occur if a quality of beam pairlink(s) of at least one PDCCH falls below a threshold. The thresholdcomprise be an RSRP value (e.g., −140 dbm, −110 dbm, or any other value)and/or a SINR value (e.g., −3 dB, −1 dB, or any other value), which maybe configured in a RRC message.

FIG. 20A shows an example of a first beam failure event. A base station2002 may send (e.g., transmit) a PDCCH from a transmission (Tx) beam toa receiving (Rx) beam of a wireless device 2001 from a TRP. The basestation 2002 and the wireless device 2001 may start a beam failurerecovery procedure on the TRP, for example, if the PDCCH on the beampair link (e.g., between the Tx beam of the base station 2002 and the Rxbeam of the wireless device 2001) have a lower-than-threshold RSRPand/or SINR value due to the beam pair link being blocked (e.g., by amoving vehicle 2003, a building, or any other obstruction).

FIG. 20B shows an example of a second beam failure event. A base stationmay send (e.g., transmit) a PDCCH from a beam to a wireless device 2011from a first TRP 2014. The base station and the wireless device 2011 maystart a beam failure recovery procedure on a new beam on a second TRP2012, for example, if the PDCCH on the beam is blocked (e.g., by amoving vehicle 2013, building, or any other obstruction).

A wireless device may measure a quality of beam pair links using one ormore RSs. The one or more RSs may comprise one or more SS blocks and/orone or more CSI-RS resources. A CSI-RS resource may be determined by aCSI-RS resource index (CRI). A quality of beam pair links may beindicated by, for example, an RSRP value, a reference signal receivedquality (e.g., RSRQ) value, and/or a CSI (e.g., SINR) value measured onRS resources. A base station may indicate whether an RS resource, usedfor measuring beam pair link quality, is QCLed (Quasi-Co-Located) withDM-RSs of a PDCCH. The RS resource and the DM-RSs of the PDCCH may beQCLed, for example, if the channel characteristics from a transmissionon an RS to a wireless device, and that from a transmission on a PDCCHto the wireless device, are similar or same under a configuredcriterion. The RS resource and the DM-RSs of the PDCCH may be QCLed, forexample, if Doppler shift and/or Doppler shift of the channel from atransmission on an RS to a wireless device, and that from a transmissionon a PDCCH to the wireless device, are the same.

A wireless device may monitor a PDCCH on M beams (e.g. 2, 4, 8) pairlinks simultaneously, where M≥1 and the value of M may depend at leaston capability of the wireless device. Monitoring a PDCCH may comprisedetecting DCI via the PDCCH transmitted on common search spaces and/orwireless device specific search spaces. Monitoring multiple beam pairlinks may increase robustness against beam pair link blocking. A basestation may send (e.g., transmit) one or more messages comprisingparameters indicating a wireless device to monitor PDCCH on differentbeam pair link(s) in different OFDM symbols.

A base station may send (e.g., transmit) one or more RRC messages and/orMAC CEs comprising parameters indicating Rx beam setting of a wirelessdevice for monitoring PDCCH on multiple beam pair links. A base stationmay send (e.g., transmit) an indication of a spatial QCL between DL RSantenna port(s) and DL RS antenna port(s) for demodulation of DL controlchannel. The indication may comprise a parameter in a MAC CE, an RRCmessage, DCI, and/or any combinations of these signaling.

A base station may indicate spatial QCL parameters between DL RS antennaport(s) and DM-RS antenna port(s) of DL data channel, for example, forreception of data packet on a PDSCH. A base station may send (e.g.,transmit) DCI comprising parameters indicating the RS antenna port(s)are QCLed with DM-RS antenna port(s).

A wireless device may measure a beam pair link quality based on CSI-RSsQCLed with DM-RS for PDCCH, for example, if a base station sends (e.g.,transmits) a signal indicating QCL parameters between CSI-RS and DM-RSfor PDCCH. The wireless device may start a BFR procedure, for example,if multiple contiguous beam failures occur.

A wireless device may send (e.g., transmit) a BFRQ signal on an uplinkphysical channel to a base station, for example, if starting a BFRprocedure. The base station may send (e.g., transmit) DCI via a PDCCH ina CORESET, for example, after or in response to receiving the BFRQsignal on the uplink physical channel. The wireless may determine thatthe BFR procedure is successfully completed, for example, after or inresponse to receiving the DCI via the PDCCH in the CORESET.

A base station may send (e.g., transmit) one or more messages comprisingconfiguration parameters of an uplink physical channel, or signal, fortransmitting a beam failure recovery request. The uplink physicalchannel or signal may be based on one of: a contention-free PRACH(BFR-PRACH), which may be a resource orthogonal to resources of otherPRACH transmissions; a PUCCH (e.g., BFR-PUCCH); and/or acontention-based PRACH resource (e.g., CF-PRACH). Combinations of thesecandidate signals and/or channels may be configured by the base station.A wireless device may autonomously select a first resource fortransmitting the BFRQ signal, for example, if the wireless device isconfigured with multiple resources for a BFRQ signal. The wirelessdevice may select a BFR-PRACH resource for transmitting a BFRQ signal,for example, if the wireless device is configured with the BFR-PRACHresource, a BFR-PUCCH resource, and/or a CF-PRACH resource. The basestation may send (e.g., transmit) a message to the wireless deviceindicating a resource for transmitting the BFRQ signal, for example, ifthe wireless device is configured with a BFR-PRACH resource, a BFR-PUCCHresource, and/or a CF-PRACH resource.

A base station may send (e.g., transmit) a response to a wirelessdevice, for example, after receiving one or more BFRQ signals. Theresponse may comprise the CRI associated with the candidate beam thatthe wireless device may indicate in the one or multiple BFRQ signals. Abase station and/or a wireless device may perform one or more beammanagement procedures, for example, if the base station and/or thewireless device are configured with multiple beams (e.g., in system suchas in an NR system). The wireless device may perform a beam failurerecovery (BFR) procedure (e.g., send one or more BFRQ signals), forexample, if one or more beam pair links between the base station and thewireless device fail.

FIG. 21 shows an example BFR procedure. At step 2101, a wireless devicemay receive one or more messages (e.g., RRC messages) comprising one ormore BFR parameters. Although described in connection with a single beamfailure, BFR procedures such as the procedure of FIG. 21 may beperformed in connection with multiple (e.g., simultaneous) beamfailures. At step 2102, the wireless device may detect a beam failureaccording to one or more BFR parameters, for example, at least one ofthe BFR parameters received at step 2101. The wireless device may starta first timer, for example, after or in response to detecting the beamfailure. At step 2103, the wireless device may select a selected beam,for example, a beam, from a set of candidate beams, with good channelquality (e.g., based on one or more of RSRP, SINR, or BLER). Thecandidate beams may be identified by a set of reference signals (e.g.,SSBs and/or CSI-RSs). The wireless device may select the selected beam,for example, after or in response to detecting the beam failure. At step2104, the wireless device may send (e.g., transmit) one or more BFRsignals to a base station (e.g., a gNB), for example, after or inresponse to the selecting the selected beam. The one or more BFR signalsmay be associated with the selected beam. The wireless device maytransmit the one or more BFR signals with a transmission beamcorresponding to a receiving beam associated with the selected beam. Theone or more BFR signals may comprise, for example, one or more of: apreamble transmitted on a PRACH resource, a SR signal transmitted on aPUCCH resource, a beam failure recovery signal transmitted on a PUCCHresource, or a beam report transmitted on a PUCCH/PUSCH resource. Thewireless device may start a response window, for example, after or inresponse to transmitting the one or more BFR signals. The responsewindow may be a timer with a value configured (or determined) by thebase station. At step 2105, the wireless device may monitor a PDCCH in afirst CORESET. The wireless device may monitor the PDCCH in the firstCORESET, for example, if the response window is running. The firstCORESET may be associated with the BFR procedure. The wireless devicemay monitor the PDCCH in the first CORESET, for example, in condition ofsending (e.g., transmitting) the one or more BFR signals. At step 2106,the wireless device may receive first DCI via the PDCCH in the firstCORESET, for example, during the response window (e.g., if the responsewindow is running). At step 2017, the wireless device may determine thatthe BFR procedure is successfully completed, for example, after or inresponse to receiving the first DCI via the PDCCH in the first CORESET.The wireless device may stop the timer and/or stop the response window,for example, after or in response to the BFR procedure successfullybeing completed.

At step 2106, if the wireless device does not receive the DCI (e.g.,before the response window expires), the wireless device may increment atransmission number. The transmission number may be initialized to afirst number (e.g., 0) before the BFR procedure is triggered. At step2108, the wireless device may determine if the transmission numbersatisfies (e.g., indicates a number less than) a predetermined value(e.g., a configured maximum transmission number). If the transmissionnumber satisfies the predetermined value, the wireless device may repeatone or more of steps 2104, 2105, 2106, or 2108 by, e.g., performingactions comprising at least one of: sending (e.g., transmitting) a BFRsignal, starting a response window (e.g., a timer), monitoring thePDCCH, determining if DCI is received, or incrementing the transmissionnumber if no DCI is received (e.g., during the response window and/orwhile the timer is running). If at step 2108 the transmission numberdoes not satisfy the predetermined value (e.g., if the transmissionnumber indicates a number equal or greater than the predeterminedvalue), the wireless device may at step 2109 declare that the BFRprocedure is unsuccessfully completed.

A MAC entity of a wireless device may be configured (e.g., by an RRClayer) with a BFR procedure. The BFR procedure may be used forindicating, to a serving base station, a new SSB and/or a new CSI-RS ifa beam failure is detected on one or more serving SSBs and/or CSI-RSs ofthe serving base station. The beam failure may be detected, for example,by counting at least one beam failure instance indication from a lowerlayer of the wireless device (e.g., a PHY layer) to the MAC entity.

An RRC layer may configure a wireless device with one or more of thefollowing parameters in a BeamFailureRecoveryConfig for a beam failuredetection procedure and/or a BFR procedure: beamFailurelnstanceMaxCountfor a beam failure detection, beamFailureDetectionTimer for the beamfailure detection, beamFailureCandidateBeamThreshold (e.g., an RSRPthreshold for a beam failure recovery), preamblePowerRampingStep for theBFR, preambleReceivedTargetPower for the BFR, preambleTxMax for the BFR,or an ra-ResponseWindow. The ra-ResponseWindow may be a time window tomonitor one or more responses for the BFR using a contention-free RandomAccess preamble.

A wireless device may, for example, use at least one variable (e.g., aUE variable) for a beam failure detection. A BFI_COUNTER may be one ofthe at least one variables used. The BFI_COUNTER may be a counter forbeam failure instance indication. The BFI_COUNTER may be initially setto zero.

If a MAC entity of a wireless device receives a beam failure instanceindication from a lower layer of the wireless device, the wirelessdevice may start or restart beamFailureDetectionTimer. The wirelessdevice may also (e.g., in conjunction with startingbeamFailureDetectionTimer) or alternatively increment BFI_COUNTER byone. The wireless device may initiate a Random Access procedure on anSpCell based on the BFI_COUNTER being equal tobeamFailurelnstanceMaxCount+1. The wireless device may apply theparameters in the BeamFailureRecoveryConfig based on initiating theRandom Access procedure. If the beamFailureDetectionTimer expires, thewireless device may set the BFI_COUNTER to zero. If the Random Accessprocedure is successfully completed, the wireless device may considerthe beam failure recovery procedure successfully completed.

If a MAC entity of a wireless device sends (e.g., transmits) acontention-free random access preamble for a BFRQ, the MAC entity maystart an ra-ResponseWindow at a PDCCH, for example, a first PDCCHoccasion following the end of the transmitting the contention-freerandom access preamble. The ra-ResponseWindow may be configured inBeamFailureRecoveryConfig. The wireless device may, for example, if thera-ResponseWindow is running, monitor at least one PDCCH of an SpCellfor a response to the BFRQ. The BFRQ may be identified by a C-RNTI. If anotification of a reception of a PDCCH transmission is received from alower layer of the wireless device, if the PDCCH transmission isaddressed to a C-RNTI, and if a contention-free random access preamblefor a BFRQ was sent (e.g., transmitted) by a MAC entity of the wirelessdevice, the wireless device may consider the random access proceduresuccessfully completed.

A wireless device may initiate a contention-based random access preamblefor a BFRQ. A MAC entity of the wireless device may start ara-ContentionResolutionTimer if, for example, the wireless devicetransmits Msg3. The ra-ContentionResolutionTimer may be configured bythe RRC layer. The wireless device may, for example, based on startingthe ra-ContentionResolutionTimer, monitor at least one PDCCH if thera-ContentionResolutionTimer is running. The wireless device mayconsider the random access procedure successfully completed, forexample, if a notification of a reception of a PDCCH transmission isreceived from a lower layer of the wireless device, if a C-RNTI MAC-CEis included in the Msg3, and/or if a random access procedure wasinitiated for a BFR procedure and the PDCCH transmission is addressed toa C-RNTI of the wireless device. The wireless device may, for example,based on the random access procedure being successfully completed, stopthe ra-ContentionResolutionTimer. If a random access procedure of a BFRprocedure is successfully completed, the wireless device may considerthe BFR procedure successfully completed.

A wireless device may be configured (e.g., for a serving cell) with afirst set of periodic CSI-RS resource configuration indexes by a higherlayer parameter Beam-Failure-Detection-RS-ResourceConfig. The wirelessdevice may also or alternatively be configured with a second set ofCSI-RS resource configuration indexes and/or SS/PBCH block indexes by ahigher layer parameter Candidate-Beam-RS-List. The first set and/or thesecond set may be used for radio link quality measurements on theserving cell. The wireless device may determine, for example, if thewireless device is not provided with a higher layer parameterBeam-Failure-Detection-RS-ResourceConfig, a first set to include SS/PBCHblock indexes and periodic CSI-RS resource configuration indexes. TheSS/PBCH block indexes and the periodic CSI-RS resource configurationindexes may comprise values that are the same as one or more RS indexesin one or more RS sets. The one or more RS indexes in the one or more RSsets may be indicated, for example, by one or more TCI states. The oneor more TCI states may, for example, be used for respective CORESETswith which the wireless device is configured for monitoring PDCCH. Thewireless device may, for example, expect a single port RS in the firstset.

A first threshold (e.g., Qout,LR) may, for example, correspond to afirst default value of a higher layer parameterRLM-IS-OOS-thresholdConfig. A second threshold (e.g., Qin,LR) may, forexample, correspond to a second default value of a higher layerparameter Beam-failure-candidate-beam-threshold. A physical layer in thewireless device may assess a first radio link quality according to thefirst set of periodic CSI-RS resource configurations against the firstthreshold. For the first set, the wireless device may assess the firstradio link quality according to periodic CSI-RS resource configurationsand/or SS/PBCH blocks. The periodic CSI-RS resource configurationsand/or the SS/PBCH blocks may, for example, be associated (e.g., quasico-located) with at least one DM-RS of a PDCCH monitored by the wirelessdevice.

A wireless device may, for example, apply the second threshold to afirst layer-1 reference signal received power (L1-RSRP) for SS/PBCHblocks. The wireless device may apply the second threshold to a secondL1-RSRP for periodic CSI-RS resources based on, for example, after,scaling a respective CSI-RS reception power with a value provided by ahigher layer parameter Pc_SS.

A physical layer in a wireless device may, for example, in slots wherethe first radio link quality according to the first set is assessed,provide an indication to higher layers (e.g., the MAC layer). Thewireless device may provide an indication to higher layers if the firstradio link quality for all corresponding resource configurations in thefirst set is worse than the first threshold. The wireless device may usethe corresponding resource configurations in the first set to assess thefirst radio link quality. The physical layer may inform the higherlayers (e.g. the MAC layer and/or the RRC layer) when the first radiolink quality is worse than the first threshold with a first periodicity.The first periodicity may be determined, for example, by a maximumbetween the shortest periodicity of periodic CSI-RS configurations orSS/PBCH blocks in the first set and a predetermined value (e.g., 10 ms).

A wireless device may, for example, based on a request from higherlayers (e.g., the MAC layer), provide to the higher layers the periodicCSI-RS configuration indexes and/or SS/PBCH block indexes from thesecond set. The wireless device may also or alternatively provide, tothe higher layers, corresponding L1-RSRP measurements that are largerthan or equal to the second threshold.

A wireless device may be configured with a CORESET by a higher layerparameter Beam-failure-Recovery-Response-CORESET. The wireless devicemay also or alternatively be configured with an associated search spaceprovided by a higher layer parameter search-space-config. The associatedsearch space may be used for monitoring a PDCCH in the CORESET. Thewireless device may receive from higher layers (e.g., the MAC layer), bya parameter Beam-failure-recovery-request-RACH-Resource, a configurationfor a PRACH transmission. For the PRACH transmission in slot n and basedon antenna port quasi co-location parameters associated with periodicCSI-RS configuration and/or SS/PBCH block with a first RS index, thewireless device may monitor the PDCCH for detection of a DCI formatstarting from slot n+4 within a window. The window may be configured bya higher layer parameter Beam-failure-recovery-request-window. The DCIformat may comprise a CRC scrambled by a C-RNTI. For a PDSCH reception,the wireless device may assume the antenna port quasi-collocationparameters (e.g., as for monitoring the PDCCH) until the wireless devicereceives, for example, via higher layers, an activation for a TCI stateand/or a parameter TCI-StatesPDCCH.

A base station may control one or more time resources and/or one or morefrequency resources that may be used by a wireless device to report CSI.The CSI may comprise a CQI, a precoding matrix indicator PMI, a CSI-RSresource indicator (CRI), a layer indication (LI), a rank indication(RI), and/or and an L1-RSRP.

For CQI, PMI, CRI, LI, RI, L1-RSRP, a wireless device may, for example,be configured by higher layers with one or more CSI-ReportConfigReporting Settings, one or more CSI-ResourceConfig Resource Settings,and/or a list of trigger states ReportTriggerList. The list of triggerstates may contain a list of associated CSI-ReportConfigs indicating theResource Set IDs for channel and/or for interference.

Each reporting setting CSI-ReportConfig may, for example, be associatedwith a single downlink BWP (e.g., indicated by a higher layer parameterbandwidthPartId). Each reporting setting may also or alternativelycontain one or more reported parameters for one CSI reporting band(e.g., CSI Type (I or II) (if reported), codebook configuration (e.g.,comprising codebook subset restriction), time-domain behavior, frequencygranularity for CQI and/or PMI, measurement restriction configurations,the layer indicator (LI), the reported L1-RSRP parameter(s), CRI, and/orSSBRI (SSB Resource Indicator)).

A time domain behavior of the CSI-ReportConfig may, for example, beindicated by a higher layer parameter reportConfigType. The time domainbehavior may be set to aperiodic, semi-persistent, or periodic CSIreporting. For periodic and semi-persistent CSI reporting, a configuredperiodicity and a slot offset may apply in a numerology of an UL BWP.The wireless device may send (e.g., transmit) the CSI report on the ULBWP. The higher layer parameter ReportQuantity may indicate CS I-relatedor L1-RSRP-related quantities to report. The parameterReportFreqConfiguration may indicate the reporting granularity in thefrequency domain, for example, the CSI reporting band and/or whetherPMI/CQI reporting is wideband or sub-band. The CSI-ReportConfigparameter may comprise timeRestrictionForChannelMeasurements enablingthe configuration of time domain restriction for channel measurementsand timeRestrictionForInterferenceMeasurements enabling theconfiguration of time domain restriction for interference measurements.The CSI-ReportConfig parameter may comprise CodebookConfig, which maycomprise configuration parameters for Type-I or Type II CSI (e.g.,codebook subset restriction), and configurations of group basedreporting.

Each CSI Resource Setting CSI-ResourceConfig may comprise aconfiguration of one or more CSI Resource Sets. Each of the one or moreCSI Resource Sets may comprise CSI-RS resources (e.g., comprised ofeither NZP CSI-RS or CSI-IM) and/or SS/PBCH Block resources used forL1-RSRP computation. The CSI Resource Setting may be located in the DLBWP identified by the higher layer parameter bwp-id. CSI ResourceSettings, for example, all CSI Resource Settings linked to a CSI ReportSetting, may have the same DL BWP.

For an L1-RSRP computation, a wireless device may, for example, beconfigured with one or more CSI-RS resources and/or one or more SS/PBCHBlock resources. For an L1-RSRP computation, a wireless device may, forexample, be configured with a CSI-RS resource setting. The CSI-RSresource setting may, for example, comprise as many as sixteen CSI-RSresource sets. Each of the sixteen CSI-RS resource sets may, forexample, comprise as many as 64 resources. A total number of differentCSI-RS resources over all resource sets may, for example, compriseand/or be limited to 128 or fewer CSI-RS resources.

For a L1-RSRP reporting, if a higher layer parameter nrofReportedRS isconfigured to be one, a reported L1-RSRP value may be defined by a 7-bitvalue. The reported L1-RSRP value may be in the range [−140, −44] dBmwith 1 dB step size. For an L1-RSRP reporting, if a higher layerparameter nrofReportedRS is configured to be larger than one, or if thehigher layer parameter group-based-beam-reporting is configured as ‘ON’,the wireless device may use differential L1-RSRP based reporting, wherea largest L1-RSRP value may use a 7-bit value in the range [−140, −44]dBm with 1 dB step size, and the differential L1-RSRP may use a 4-bitvalue. The differential L1-RSRP value may be computed with 2 dB stepsize with a reference to the largest L1-RSRP value which may be part ofthe same L1-RSRP reporting instance.

A base station may transmit, to a wireless device, one or more messagescomprising configuration parameters of one or more cells. The one ormore cells may comprise at least one PCell/PSCell and one or moreSCells. An SpCell (e.g., a PCell or a PSCell) and one or more SCellsmay, for example, operate on different frequencies and/or differentbands. An SCell may support a multi-beam operation in which a wirelessdevice may perform one or more beam management procedures (e.g., a BFRprocedure) on the SCell. The wireless device may perform a BFRprocedure, for example, if at least one of one or more beam pair linksassociated with the SCell and with the wireless device fails. ExistingBFR procedures may result in inefficiencies if there is a beam failurefor one of the one or more SCells. Existing BFR procedures may beinefficient, take a relatively long time to complete, and/or increasebattery power consumption if used for an SCell.

For PCells, a BFR procedure may mimic and/or reuse a random-accessprocedure. If a PCell random-access procedure is unsuccessfullycompleted, a wireless device may declare a radio link failure (RLF).Based on declaring the RLF, the wireless device may try to re-establisha connection with the base station (e.g., using a procedure similar tothat used when a wireless device is powered ON). A random-accessprocedure for an SCell may be initiated by a base station (e.g., via aPDCCH order). If an SCell random-access procedure is under the controlof the base station (e.g., if the wireless device does not autonomouslyinitiate the random-access procedure) and is unsuccessfully completed,the base station may be aware of the unsuccessful completion and, basedon being aware of that unsuccessful completion, able to take additionalaction.

Application of PCell BFR procedures to SCell BFR may cause problemsand/or may be impractical if, for example, a wireless device determinesan SCell beam failure and/or initiates a BFR procedure autonomously. Ifa wireless device autonomously initiates a random-access procedure aspart of an SCell BFR procedure, the base station may be unaware if theBFR procedure unsuccessfully completes. The wireless device may beunable to declare an RLF for the SCell to indicate to the base stationthat a BFR procedure for the SCell has unsuccessfully completed.

Problems may occur if a base station is unaware that a BFR procedure foran SCell has unsuccessfully completed. The base station may, forexample, continue sending uplink and/or downlink scheduling informationfor that SCell to a wireless device. Because of the beam failure on thatSCell, the wireless device may be unable to receive that schedulinginformation. Signaling overhead may be unnecessarily increased. Timeand/or frequency resources allocated to that SCell may be wasted, as thewireless device may be unable to use those resources (e.g., because itcannot receive the scheduling information). If a base station is awarethat a BFR procedure for an SCell has unsuccessfully completed, the basestation may be able to take appropriate action (e.g., deactivating theSCell, stop scheduling for the SCell, and/or initiate an aperiodic beammanagement to determine a suitable beam to serve the SCell) to mitigatesome or all of these problems.

Unsuccessful completion of a BFR procedure for the SCell may indicatethat candidate beams for that SCell are insufficient. If that BFRprocedure comprises a random access procedure initiated by the wirelessdevice, and if the wireless device is unable to declare an RLF if thatrandom access procedure fails, the base station may be unaware of theunsuccessful BFR procedure. The base station may be unable, for example,based on being unaware of the unsuccessful BFR procedure, to instructthe wireless device to discontinue monitoring of downlink signals in theSCell. The base station may similarly be unable to instruct the wirelessdevice to discontinue uplink transmissions in the SCell. If a wirelessdevice continues to monitor downlink control channels for an SCell afteran unsuccessful BFR procedure, the wireless device may unnecessarilyconsume power attempting to receive signals when no sufficient beams areavailable. If the wireless device continues performing uplinktransmissions, the wireless device may unnecessarily increase uplinkinterference (e.g., decrease signal quality) for other cells and/orother wireless devices. If downlink beams are insufficient, for example,transmitting uplink signals via the SCell may be useless if the wirelessdevice is not able to receive acknowledgment (ACK) of such uplinksignals.

An SCell may be configured for a wireless device with a deactivationtimer controlling activation status of the SCell (e.g., by deactivatingthe SCell if DCI indicating an uplink grant (for an uplink datatransmission) or a downlink assignment (for a downlink datatransmission) is not received before the timer expiration). If adeactivation timer is used for an SCell, and a wireless device takes noother action if a BFR procedure for that SCell unsuccessfully completes,the SCell may be deactivated based on expiration of the timer. An SCelldeactivation timer may have a relatively long duration (e.g., 1024 ms),and the above described problems (e.g., interference, power consumption)may continue if the timer is unexpired and a BFR procedure has notsucceeded. Shortening the duration of an SCell deactivation timer maycause other problems. If duration of an SCell deactivation timer isreduced, the SCell may be deactivated frequently. Reactivating adeactivated SCell may require additional activation signaling from thebase station, and/or the wireless device may need to perform channelmeasurements based on receiving the additional activation signaling. Theadditional activation signaling and/or channel measurements may increasesignaling overhead between the base station and the wireless device, andmay also increase the latency for SCell activation.

A base station may configure an SCell for a wireless device for periodicbeam reporting. A wireless device may, for example, be configured tomeasure RSRP of M RSs of the SCell (where M may be an integer value),and to report the N RSs with highest RSRP values (where N may be equalto or less than M) based on a period T (e.g., the wireless device may beconfigured to transmit the beam report at times T, 2T, 3T, etc.). Thewireless device may send the periodic reporting via one or more PUCCHs.Values for RSRP (e.g., in dBm) may be mapped to 7-bit values (e.g., in amapping table stored by a wireless device and by a base station), asdescribed below in connection with FIG. 25. Some 7-bit values may bereserved and not used for reporting of RSRP values (and/or not used forother types of values associated with beam reporting). One or morereserved values may be used to indicate unsuccessful completion of anSCell BFR procedure, as described below. The wireless device may includethe one or more reserved values, for example, in beam reporting that thewireless device sends to a PCell and/or to another cell different fromthe SCell for which a beam failure was determined. The base station maydetermine, based on the one or more reserved values sent by the wirelessdevice, that a BFR procedure has unsuccessfully completed for the SCellwhere the beam failure was determined. The base station may, based ondetermining that unsuccessful completion, take appropriate action (e.g.,deactivate the SCell for the wireless device, discontinue sending ofuplink and/or downlink scheduling information to the wireless device forthat SCell, reallocate time and/or frequency resources). Based ondetermining unsuccessful completion of a BFR procedure for the SCell,the wireless device may, for example, without waiting for expiration ofa deactivation timer for that SCell, discontinue monitoring downlinkcontrol channels for that SCell and/or may take other action. Radioefficiency may be improved, signaling overhead may be reduced, spuriousand/or unnecessary uplink and/or downlink transmissions may be reduced,and/or consumption of the wireless device's battery power may bereduced.

If a wireless device is configured with an SCell comprisingdownlink-only resources, a wireless device may be unable to send (e.g.,transmit) an uplink signal (e.g., a preamble) in that SCell for a BFRprocedure if a beam failure occurs on the SCell. The wireless device maybe unable to perform a BFR procedure on that SCell, and a base stationmay not become aware of the beam failure on that SCell. Including avalue (e.g., a reserved value, as described above) in signaling sent bythe wireless device to a PCell (and/or another cell different from theSCell) may be used to inform the base station of the beam failure.

An SCell may, for example, operate in a higher frequency band (e.g. 23GHz, 60 GHz, 70 GHz). An SpCell may, for example, operate in a lowerfrequency band (e.g. 2.4 GHz, 5 GHz). The channel condition of the SCellmay be different from the channel condition of the SpCell. The wirelessdevice may use uplink resources of the SpCell to send (e.g., transmit) apreamble for a beam failure recovery request for the SCell, to improverobustness of transmission of the preamble. BFR procedures may beenhanced for an SCell operating in a different frequency band than anSpCell. That SCell (e.g., an SCell for which an uplink control channelis not configured) may be configured to send beam reporting via uplinkcontrol channels of that SpCell (e.g., a PCell). Even if there is a beamfailure in the SCell, there may no problem with the SpCell, andindicating unsuccessful completion of a BFR for the SCell, via theperiodic beam reporting on the SpCell, may be reliable and robust.

A wireless device may be configured with a BFR timer that may be used,for example, to limit a duration of a BFR procedure. The wireless devicemay be configured with an SCell deactivation timer that is used, forexample, to cause deactivation of the SCell (e.g., if no DCI has beenreceived). The duration of the SCell deactivation timer (e.g., 1280 ms)may be greater than that of the BFR timer (e.g., 200 ms). If a BFRprocedure of an SCell fails, for example due to an expiry of the BFRtimer, the wireless device may continue to perform uplink transmissionsand/or monitor downlink transmissions via the SCell until the SCelldeactivation timer expires. A time gap between the expiry of the BFRtimer and an expiry of the SCell deactivation timer may be relativelylarge (e.g., approximately 1000 ms). During the time gap, the wirelessdevice may cause uplink interference to other users/cells. During thetime gap, the wireless device may, for example, miss one or more DCItransmitted by the base station on at least one PDCCH of the SCell. Thismay result in a high power consumption of the wireless device and/orsignaling overhead of the base station.

Additional operations of a wireless device, during a time gap betweenthe expiry of the BFR timer and an expiry of the SCell deactivationtimer, may cause inefficiencies and/or other problems. A wireless devicemay, for example, use a DL SCell as a pathloss reference for an ULtransmission and may observe a poor radio link quality (e.g., higherthan % 10 BLER) on the DL SCell. The poor radio link quality may, forexample, be caused by a beam failure. The beam failure may be associatedwith one or more downlink control channels of the DL SCell. If thewireless device continues to use the DL SCell with the poor radio linkquality as the pathloss reference for the UL transmission, the wirelessdevice may generate unnecessary interference due to spurious uplinktransmissions. A wireless device may be out of synchronization, forexample based on a beam failure, on a DL SCell. The wireless device maygenerate spurious uplink transmissions based on being out ofsynchronization in the downlink channel, and the spurious uplinktransmissions may generate interference to other users/cells. A basestation may send (e.g., transmit), to a wireless device, transmit powercontrol commands for an uplink transmission of an SCell. If there is abeam failure for that SCell, the wireless device may not receive thetransmit power control commands on one or more downlink control channelsof that SCell, and/or the transmit power control commands received bythe wireless device may be unreliable. Based on unreceived or unreliabletransmit power control commands, the wireless device may fail toproperly control power of the uplink transmission of the SCell. This mayresult in interference to other users/cells.

A wireless device may discontinue, based on expiration of a BFR timerand/or other determination of an unsuccessfully completed BFR procedure,UL transmissions in an SCell associated with a beam failure. Thewireless device may discontinue those UL transmissions in the SCellprior to expiration of an SCell deactivation timer that may beconfigured for the SCell. The wireless device may discontinue those ULtransmissions independently of whether a base station is made aware ofthe unsuccessfully completed BFR procedure. A wireless device may alsoor alternatively discontinue, based on expiration of the BFR timerand/or other determination of the unsuccessfully completed BFRprocedure, monitoring of DL transmissions in that SCell. The wirelessdevice may discontinue monitoring those DL transmissions prior toexpiration of the SCell deactivation timer that may be configured forthe SCell. The wireless device may discontinue monitoring those DLtransmissions independently of whether the base station is made aware ofthe unsuccessfully completed BFR procedure. By such discontinuing of ULtransmissions and/or monitoring of DL transmissions, inefficiencies andother problems (e.g., as described above) may be reduced.

A base station may not detect a beam failure or a failure of a BFRprocedure for an SCell using a CQI report and/or a configured radioresource management (RRM) measurement report for the SCell. The CQIreport and/or the configured RRM report may, for example, be lost ordelayed. A wireless device sending (e.g., transmitting) an alternateand/or additional uplink notification of a failure of a BFR for an SCellto a base station may enable the base station to detect the BFR failurefor the SCell more rapidly (e.g., more rapidly than a CQI report and/oran RRM report). The alternate and/or additional uplink notification maycomprise including a value (e.g., a reserved value, as described herein)in signaling sent by the wireless device to a PCell (and/or another celldifferent from the SCell).

As described above, a wireless device may stop uplink transmissions foran SCell based on determining a failure of a BFR procedure for thatSCell. Based on stopping the uplink transmissions, the wireless devicemay transmit an uplink notification of a failure of a BFR procedure forthe SCell via uplink resources of a first cell (e.g. PCell).

A wireless device that has stopped uplink transmissions of an SCell,based on a failure of a BFR procedure of that SCell, may autonomouslyresume the uplink transmissions if a radio quality of at least onedownlink channel of the SCell recovers (e.g., before an SCelldeactivation timer of that SCell expires). The recovery of the at leastone downlink channel of the SCell may comprise, for example, receivingDCI on the at least one downlink channel of the SCell.

A wireless device may, based on a failure of a BFR for an SCell, stopmonitoring at least one PDCCH in the one or more CORESETs of the SCell.The one or more CORESETs may comprise a dedicated CORESET and/or acommon CORESET. The dedicated CORESET may be used, for example, toreceive a response (e.g., DCI) from a base station to complete a BFRprocedure. The stopping monitoring the at least one PDCCH may result ina reduced power consumption of the wireless device.

Based on receiving an uplink notification of a failure of a BFRprocedure for an SCell, a base station may deactivate and/or release theSCell. The deactivating and/or the releasing of the SCell may beperformed via MAC CE signaling. Based on receiving the uplinknotification, for example, the base station may stop scheduling thewireless device on the SCell. The stopping of the scheduling on theSCell may avoid waste of resources due to unnecessary scheduling.

Based on a failure of a BFR procedure for an SCell, a wireless devicemay autonomously deactivate the SCell. Based on deactivating the SCell,the wireless device may send (e.g., transmit) an uplink notification ofthe failure of the BFR procedure for the SCell via uplink resources of afirst cell (e.g. PCell).

An uplink notification of a failure of a BFR procedure for an SCell maybe based on beam reporting via a PUCCH, an RRC message, and/or a MAC CE.The uplink notification may comprise an identity of the SCell associatedwith the beam failure.

A detection of a beam failure instance may, for example, be based onhypothetical PDCCH BLER. Using beam reporting via a PUCCH, a wirelessdevice may report one or more L1-RSRP values associated with one or morefirst RSs. The one or more first RSs may be associated with one or moresecond RSs (e.g., one or more DM-RSs) of at least one PDCCH. The basestation may be unable to determine, based on values in the PUCCH beamreporting that indicate actual values (e.g., actual L1-RSRP values), abeam failure instance. A wireless device may, for example, assess a lowBLER (e.g., higher than % 10 BLER) on the at least one PDCCH, but thatat least one PDCCH may have a high L1-RSRP. The base station may not beable to determine, based on the high L1-RSRP reported via the PUCCH, thelow BLER on the at least one PDCCH. To notify a base station of afailure of a BFR procedure of an SCell using a PUCCH beam reporting, awireless device may include a value (e.g., a reserved value) in suchreporting that does not indicate an actual value.

FIG. 22 shows an example timeline for an example BFR procedure. The BFRprocedure may, for example, be for an SCell and/or may successfullycomplete. FIG. 23 is a flowchart showing steps of an example BFRprocedure. The example timeline of FIG. 22 may, for example, beassociated with the example procedure of FIG. 23. For convenience, FIG.22 may indicate multiple operations occurring at a single time. Multipleoperations associated with a single time of the FIG. 22 timeline neednot occur at the same instant or within a specific amount of time, andneed not occur in a specific order relative to one another. The order ofoperations shown in FIG. 22, and/or of steps shown in FIG. 23, may bevaried. One or more of the operations and/or steps may be modified oromitted, and/or other operations and/or steps may be added.

At step 2301 (FIG. 23), and as shown at time T0 (FIG. 22), a wirelessdevice 2201 may receive (e.g., from a base station) one or more messagescomprising configuration parameters. The wireless device may receive theone or more messages via a first cell 2200 (e.g., a PCell). The one ormore messages may comprise one or more RRC messages (e.g. an RRCconnection reconfiguration message, an RRC connection reestablishmentmessage, and/or an RRC connection setup message). The configurationparameters may comprise one or more BFR configuration parameters. Theone or more BFR configuration parameters may comprise a first set of RSresource configurations for a second cell 2202 (e.g., an SCell). Thefirst set of RS resource configurations may comprise one or more firstRSs (e.g., CSI-RS and/or SS blocks) of the second cell 2202. The one ormore BFR configuration parameters may comprise a second set of RSresource configurations comprising one or more second RSs (e.g., CSI-RSand/or SS blocks) of the second cell 2202. The wireless device 2201 maymeasure radio link quality of one or more beams associated with the oneor more first RSs and/or the one or more second RSs. The one or more BFRconfiguration parameters may comprise one or more beam failure recoveryrequest (BFRQ) resources associated with the second cell 2202. The BFRQresources may, for example, be on the first cell 2200 (e.g., if thesecond cell 2202 is configured without uplink resources for the wirelessdevice 2201). The BFRQ resources may be on the second cell 2202. The oneor more BFR configuration parameters may comprise an association betweeneach of the one or more second RSs and each of the one or more BFRQresources. The one or more messages received at step 2301, and/or othermessages received from the base station, may comprise configurationparameters defining and/or otherwise indicating reporting (e.g., beamreporting as described below) to be performed by the wireless device.

A base station may, for example, if configured with carrier aggregation(CA), send (e.g., transmit), to the wireless device 2201, an SCellActivation/Deactivation MAC CE activating the second cell 2202. At step2302 (FIG. 23), the wireless device 2201 may determine if a MAC CE forsecond cell activation has been received. If not, and as shown at step2304, the wireless device 2201 may continue operating on the first cell2200 (e.g., only on the first cell 2200) and/or on other SCells alreadyactivated. If a MAC CE for activation of the second cell 2202 isreceived (e.g., an SCell Activation/Deactivation MAC CE), and as shownat time T1 (FIG. 22), the wireless device 2201 may at step 2305 (FIG.23) activate the second cell 2202. Based on receiving the MAC CE (e.g.,an SCell Activation/Deactivation MAC CE) for activation of the secondsell 2202, the wireless device 2201 may (e.g., at time T1) start orrestart an SCell deactivation timer associated with the second cell2202.

The wireless device 2201 may, for example, assess a first radio linkquality of the one or more first RSs (e.g., First RS 1 and/or First RS 2in FIG. 22) of the second cell 2202 against a first threshold. The firstthreshold (e.g., a threshold value of hypothetical BLER, a thresholdvalue of L1-RSRP) may be a first value provided by a higher layer (e.g.,an RRC layer, a MAC layer). The wireless device 2201 may monitor atleast one PDCCH of the second cell 2202. At least one RS (e.g., a DM-RS)of the at least one PDCCH may be associated with (e.g., QCLed) the oneor more first RSs. At step 2306 (FIG. 23), the wireless device 2201determine if a BFR procedure is initiated for the second. If not, atstep 2307 the wireless device may continue to operate on the first cell2200 and the second cell 2202.

The wireless device 2201 may detect a beam failure on the second cell2202 if, for example, a first radio link quality of the one or morefirst RSs meets one or more predetermined criteria. A beam failure mayoccur, for example, if RSRP and/or SINR of the one or more first RSs islower than the first threshold and/or if BLER is higher than the firstthreshold. The determination of beam failure may be based on evaluationsof RSRP, SINR, BLER, and/or other characteristics for a quantity ofmultiple consecutive RSs. A beam failure may be determined, for example,if all evaluations of the quantity of multiple consecutive RSs meet theone or more predetermined criteria. The quantity of may be provided by ahigher layer (e.g., an RRC layer, a MAC layer).

Based on determining a beam failure on the second cell, and as shown attime T2 in FIG. 22, the wireless device 2201 may initiate a BFRprocedure (e.g., a random access procedure) of the second cell 2202.Based on initiating the BFR procedure, the wireless device 2201 may atstep 2308 (FIG. 23), and as also shown at time T2 (FIG. 22), start a BFRtimer (if configured) and/or initiate a candidate beam identificationprocedure. For the candidate beam identification procedure, the wirelessdevice 2201 may identify a first RS (e.g., the Second RS 2) in the oneor more second RSs. The first RS may be associated with a BFRQ resourceof the one or more BFRQ resources. The BFRQ resource may comprise atleast one preamble and at least one PRACH resource (e.g., time and/orfrequency). A second radio link quality (e.g., based on BLER and/orL1-RSRP) of the first RS may, for example, be better (e.g., a lower BLERvalue, a higher L1-RSRP value, and/or a higher SINR value) than a secondthreshold. The second threshold may, for example, be a second valueprovided by the higher layer (e.g., the RRC layer, the MAC layer).

Based on detecting the beam failure on the second cell 2202 and onidentifying the first RS of the second cell 2202, the wireless device2201 may at step 2309 initiate a BFRQ transmission. The BFRQtransmission may comprise sending (e.g., transmitting), in a first slot,the at least one preamble via the at least one PRACH resource for theBFR procedure of the second cell. The BFRQ transmission is shown at timeT3 of FIG. 22. The at least one PRACH resource may, for example, be onthe first cell 2200 (e.g., if the second cell 2202 is an SCell for whichthe wireless device 2201 is not configured for uplink transmission). Theat least one PRACH resource may be on the second cell 2202 (e.g., if thesecond cell 2202 is an SCell for which the wireless device 2201 isconfigured for uplink transmission).

At step 2310, and based on sending (e.g., transmitting) the at least onepreamble in the first slot, the wireless device 2201 may start, from asecond slot, monitoring for a BFR response. The monitoring for the BFRresponse may comprise monitoring at least one second PDCCH in one ormore CORESETs for first DCI (e.g. a downlink assignment or an uplinkgrant) within a configured response window. The first DCI may be withCRC scrambled by a C-RNTI of the wireless device 2201.

The one or more CORESETs may, for example, be on the first cell 2200. Awireless device 2201 may monitor the at least second PDCCH of the firstcell 2200 in the one or more CORESETs according to an antenna portassociated (e.g., QCLed) with at least one third RS. The at least onethird RS may, for example, be selected from one or more third RSs of thefirst cell 2200. At least one fourth RS (e.g., a DM-RS) of the at leastsecond PDCCH may be associated (e.g., QCLed) with the at least one thirdRS. A base station may transmit an indication of QCL between antennaport(s) of the at least one third RS and the at least one fourth RS.

The one or more CORESETs may be on the second cell. The wireless device2201 may monitor the at least second PDCCH of the second cell 2202 inthe one or more CORESETs according to an antenna port associated (e.g.,QCLed) with the first RS selected in the candidate beam identificationprocedure. At least one fourth RS (e.g., a DM-RS) of the at least secondPDCCH may be associated (e.g., QCLed) with the first RS. A base stationmay transmit an indication of QCL between antenna port(s) of the firstRS and the at least one fourth RS.

If BFR response is not received, the wireless device 2201 may at step2311 determine if a maximum number of BFRQ signal transmissions havebeen sent for the current BFR procedure, and/or if the BFR timer startedat step 2308 has expired. The maximum number or BFRQ transmissions maybe configured by a higher layer. If the maximum number of BFRQ signaltransmissions have been sent, and/or if the BFR timer has expired, thewireless device 2201 may perform steps 2313 and/or 2314, which arediscussed below in connection with FIG. 24. If the maximum number ofBFRQ signal transmissions have not been sent, and/or if the BFR timerhas not expired, the wireless device 2201 may repeat step 2309 and sendanother BFRQ signal.

If a BFR response (e.g., DCI) is received in step 2310, the wirelessdevice 2201 may determine at step 2312 that the BFR procedure issuccessfully completed. Receipt of a BFR response and successfulcompletion of the BFR procedure are shown at time T4 of FIG. 22. Adetermination of successful completion of the BFR procedure may, forexample, be based on receiving, within a configured response window,first DCI on the at least one second PDCCH in the one or more CORESETs.

FIG. 24 shows an example timeline for an example BFR procedure. The BFRprocedure of FIG. 24 may, for example, be a BFR procedure such as isdescribed in connection with FIGS. 22 and/or 23, but in which a BFRprocedure for the second cell 2202 fails (e.g., unsuccessfullycompletes). For convenience, FIG. 24 may indicate multiple operationsoccurring at a single time. Multiple operations associated with a singletime of the FIG. 24 timeline need not occur at the same instant orwithin a specific amount of time, and need not occur in a specific orderrelative to one another. The order of operations shown in FIG. 24 may bevaried. One or more of the operations shown in FIG. 24 may be modifiedor omitted, and/or other operations may be added.

Operations associated with times T0, T1, T2, and T3 in FIG. 24 may bethe same as or similar to the operations described in connection withtimes T0, T1, T2, and T3 in FIG. 22, and may be associated with steps ofFIG. 23 discussed in connection with times T0, T1, T2, and T3 in FIG.22. In the example of FIG. 24, a maximum number of BFRQ transmission(e.g., preamble transmissions) for the BFR procedure may be sent fromtime T3 to time T4, and/or the BFR timer may expire at time T4, withoutthe BFR procedure being successfully completed (e.g., without receipt ofDCI in response to a sent preamble). At step 2311 (FIG. 23), and basedon determining that the maximum number of BFRQ transmissions have beensent and/or that the BFR timer has expired without receipt of a responseto a BFRQ transmission, and/or based on other determination(s), thewireless device 2201 may at step 2313 determine that the BFR procedurehas unsuccessfully completed.

At step 2314, based on determining that the BFR procedure completedunsuccessfully, the wireless device 2201 may indicate a failure of theBFR procedure to a base station. The wireless device may, for example,and as shown at time T5 of FIG. 24, use periodic PUCCH beam reportingvia the first cell 2200 (e.g., a PCell) to send the indication.

A base station may, based on receiving an indication of the failure of aBFR procedure for the second cell 2202, deactivate and/or release thesecond cell 2202. The deactivating and/or releasing the second cell 2202may, for example, be performed via MAC CE signaling. Based on receivingthe indication, the base station may also or alternatively stopscheduling the wireless device 2201 on the second cell 2202. Thestopping of the scheduling on the second cell 2202 may avoid a waste ofresources for unnecessary scheduling.

The wireless device 2201 may, based on determining the failure of theBFR for the second cell 2202, stop uplink transmissions for the secondcell 2202. The stopping of the uplink transmissions may limitinterference to other cells and/or wireless devices. The wireless device2201 may, based on determining the failure of the BFR for the secondcell 2202, stop monitoring at least one PDCCH in the one or moreCORESETs of the second cell 2202. The stopping of monitoring the atleast one PDCCH may reduce power consumption of the wireless device2201. The wireless device may, based on determining the failure of theBFR for the second cell 2202, stop uplink transmissions of the secondcell 2202. The wireless device 2201 may continue monitoring at least onedownlink channel of the second cell 2202 if the second cell 2202 is notdeactivated (e.g., based on expiration of a second cell deactivationtimer and/or receipt of a MAC CE deactivating the second cell 2202). Thewireless device 2201 may autonomously resume the uplink transmissions inthe second cell 2202 if a radio quality of the at least one downlinkchannel of the second cell recovers.

FIG. 25 shows a table of an example mapping of L1-RSRP values to 7-bitvalues for a periodic PUCCH beam reporting. The table of FIG. 25 may,for example, be stored by a wireless device and/or by a base station. A7-bit range may accommodate 128 L1-RSRP values or value ranges (e.g.,states). Less than 128 7-bit values may be used. To report L1-RSRPvalues in the range of [−140, −44] dBm, with a 7-bit value assigned toeach 1 dB step size, another 7-bit value assigned to indicate all valuesless than −140 dBm, and another 7-bit value assigned to indicate allvalues greater than −44 dBm, 98 7-bit values may be used, leaving 307-bit values for other uses. One or more values in a range of n-bitvalues, where n is an integer, may be reserved for a notification of afailure of a beam failure of an SCell. In the example of FIG. 25, theL1-RSRP values between −140 dBm and −44 dBm may be represented with7-bit RSRP values between 0000000 and 1100001. One or more of the 7-bitvalues from 1100010 through 1111111 may be reserved for a notificationof an unsuccessful BFR procedure (and/or of a beam failure) of an SCell.For differential RSRP reporting using 4-bit values, one or more of those4-bit values (e.g., 0000 or 1111) may be used for a notification of anunsuccessful BFR procedure (and/or of a beam failure) of an SCell.

FIGS. 26B through 26D show examples of reporting indicating unsuccessfulcompletion of a BFR procedure and/or a beam failure. Reports used toindicate unsuccessful completion of a BFR procedure and/or to indicate abeam failure may be sent via a physical uplink channel (e.g., a PUCCH)and/or may include indications of measured values of characteristics(e.g., measured values for RSRP and/or L1-RSRP) associated with one ormore downlink signals (e.g., one or more RSs). The example reports ofFIGS. 26A-26B are shown as tables in which an index field is associatedwith a value field, and in which an index in that index field isassociated with a value in that value field, based adjacency of theindex and value fields in a table row. Other formats may be used toreport and/or otherwise indicate association of a value (and/or otherindicator) with an index, a cell, a beam, a signal, and/or otherelements. For example, a wireless device may be configured (e.g., viaone or more RRC messages shown at time T0 in FIGS. 22 and 24) to send(e.g., via a PUCCH) a series of values, with the order of the values inthe series respectively corresponding to indexes associated with thevalues.

A wireless device may use a PUCCH to provide beam reporting of a cell(e.g., of an SCell). The PUCCH beam reporting may comprise one or morebeam indexes and one or more measurement fields. The one or moremeasurement fields may contain values of a measured characteristic(e.g., L1-RSRP) of one or more signals (e.g., RSs) indicated by indices(e.g., beam indices) associated with the measurement fields. One or morebeam indexes may be associated (e.g., QCLed) with one or more RSs of acell associated with a beam report.

FIG. 26A shows an example beam report 2601 for a second cell (e.g., anSCell) in which the first column (“RS Set”) may comprise N beam indexfields, where N may be any integer. Each of the beam index fields maycontain an index associated with one of N RSs of the second cell. Theindices are for convenience shown in the beam report 2601 as RS 1through RS N. The second column (“L1-RSRP”) of the beam report 2601 maycomprise L1-RSRP measurement fields. In the example of FIG. 26A, each ofthe L1-RSRP measurement fields comprises a value (e.g., a 7-bit valuefrom the table of FIG. 25) mapped to a range of measured values forL1-RSRP. Each of the values of the second column may be associated withthe beam index (and may indicate an L1-RSRP value range of the RSassociated with that beam index) from the first column that is in thesame row. The value of 0001000 may, for example, be associated with thebeam index RS 1 and may indicate (e.g., based on the mapping of FIG. 25)an L1-RSRP value range for the RS associated with the beam index RS 1.In the example of FIG. 26A, no beam failure or unsuccessful BFRprocedure is reported, and each of the L1-RSRP measurement fields maycontain a non-reserved 7-bit value (e.g., one of the 7-bit valuesbetween 0000000 and 1100001 from the table of FIG. 25) mapped to anL1-RSRP value (or to a range of L1-RSRP values). The beam report 2601may be sent by a wireless device via a PUCCH of the second cell or via aPUCCH of a first cell (e.g., a PCell or another SCell).

FIG. 26B shows an example beam report 2602 for a second cell (e.g., anSCell). The beam report 2602 may, except as described below, be similarto the beam report 2601. In the example of FIG. 26B, the second cell mayhave unsuccessfully completed a BFR procedure after determining a beamfailure of the second cell. A wireless device may send the beam report2602 to indicate that unsuccessful BFR procedure for the second celland/or to indicate the beam failure. To indicate the unsuccessful BFR(and/or the beam failure), one or more of the L1-RSRP measurement fieldsin the beam report 2602 may be populated with a value (e.g., one of thereserved values (e.g., 1111111) from the table of FIG. 25) thatindicates an unsuccessful BFR procedure and/or a beam failure. A basestation that receives the beam report 2602 may determine that a BFRprocedure of the second cell was unsuccessful and/or that a beam failureoccurred in the second cell. That determination by the base station maybe based on the presence in one or more of the L1-RSRP measurementfields of values (e.g., reserved values from FIG. 25) indicating anunsuccessful BFR and/or a beam failure, and/or based data (e.g., from apreviously-sent RRC and/or other configuration message specifying timeand/or frequency resources to send the beam report 2602) indicating thatthe beam report 2602 is associated with the second cell. The basestation may, based on determining an unsuccessful BFR procedure and/orbeam failure for the second cell, send a MAC CE to deactivate the secondcell and/or may refrain from scheduling the wireless device on thesecond cell. The beam report 2602 may be sent by a wireless device via aPUCCH of the second cell or via a PUCCH of a first cell (e.g., a PCellor another SCell).

FIG. 26C shows an example beam report 2603 for a cell. The cell forwhich the report 2603 is sent and/or otherwise associated may be, forexample, a second cell (e.g., an SCell). The beam report 2603 may,except as described below, be similar to the beam report 2601. The beamreport 2603 may be sent by a wireless device via a PUCCH of the cellassociated with the beam report 2603, and/or may be sent via a PUCCH ofa another cell (e.g., a PCell or another SCell). In the example of FIG.26C, the cell associated with the report 2603 may have unsuccessfullycompleted a BFR procedure after determining a beam failure of that cell.A wireless device may send (e.g., transmit) the beam report 2603 toprovide a beam reporting of that cell and that comprises values (e.g.,non-reserved values from the table of FIG. 25) mapped to measured valuesof a characteristic (e.g., to L1-RSRP values). The beam report 2603 maycomprise an indication of a failure of random access procedure for a BFRfor that cell. A first portion of the beam report 2603 (e.g., for theindexes RS 1 through RS N) may be similar to the beam report 2601. Asecond portion of the beam report 2603 may comprise an additional beamindex (e.g., RS N+1) and an additional data field. If there is no beamfailure or failure of a BFR procedure for the cell associated with thebeam report 2603, the additional data field may be empty or may bepopulated by the wireless device with a value (e.g., one of the reservedvalues from FIG. 25) indicative of no beam failure and/or of asuccessful BFR procedure. A base station that receives the beam report2603 with the additional data field empty (or populated by the valueindicative of no beam failure and/or of a successful BFR procedure) maydetermine that there has been no beam failure for the associated celland/or that a BFR procedure of the associated cell was successful. Thatdetermination by the base station may be based on the empty additionaldata field (or the presence in that field of the value indicative of nobeam failure and/or of a successful BFR procedure), and/or based on data(e.g., from a previously-sent RRC and/or other configuration messagespecifying time and/or frequency resources to send the beam report 2603)indicating the cell with which the beam report 2603 is associated.

If a BFR procedure for the cell associated with the beam report 2603 wasunsuccessful (e.g., a random access procedure for a beam failurerecovery for the cell was unsuccessful), the wireless device maypopulate the additional data field, associated with the additional beamindex, with a value (e.g., a different one of the reserved values fromFIG. 25 (e.g., 1111111)) indicative of the unsuccessful BFR (and/or ofthe beam failure). A base station that receives the beam report 2603,with the additional data field populated by the value indicative of abeam failure and/or of an unsuccessful BFR procedure, may determine thata BFR procedure of the associated cell was unsuccessful and/or that abeam failure occurred in the cell. That determination by the basestation may be based on the presence in additional data field of thevalue indicative of the unsuccessful BFR (and/or of the beam failure),and/or based on the data indicating the cell with which the beam report2603 is associated. The base station may, based on determining thatunsuccessful BFR procedure and/or beam failure for the cell, send a MACCE to deactivate that cell and/or may refrain from scheduling thewireless device on that cell.

A wireless device may send (e.g., transmit) beam reporting (e.g., aPUCCH beam report) of a first cell (e.g., a PCell) to notify a basestation of a failure of a BFR procedure for a second cell (e.g., anSCell). That beam reporting may comprise values (e.g., non-reservedvalues from the table of FIG. 25) mapped to measured values of acharacteristic (e.g., to L1-RSRP values) for the first cell, and mayalso comprise one or more indications of one or more unsuccessful BFRprocedures (e.g., a failure of random access procedure for a BFRprocedure) for one or more second cells.

FIG. 26D shows an example beam report 2604 for a first cell (e.g., aPCell) that reports values for characteristics of the first cell, andthat may report an unsuccessful BFR procedure (and/or a beam failure)for one or more second cells. The beam report 2604 may be sent by awireless device via a PUCCH of the first cell. A first portion of thereport 2604 (e.g., for the indexes RS 1 through RS N) may be similar tothe beam report 2601, except that the first portion of the report 2604is for the first cell (e.g., for RSs associated with the first cell). Asecond portion of the beam report 2604 may comprise one or moreadditional cell index fields for cell indexes of one or more cells(e.g., cells indicated by cell indexes “Cell 1” to “Cell K”) and one ormore additional data fields respectively associated with the additionalcell index fields. Each of the one or more additional cell indexes maybe associated with a serving second cell (e.g., other than the firstcell). The serving cells may be, for example, SCells. If there is nobeam failure or a failure of a BFR procedure for a second cell indicatedby a cell index in one of the cell index fields, a wireless device mayleave empty the additional data field associated with that cell indexfield, or may populate that additional data field with a value (e.g.,one of the reserved values from FIG. 25) indicative of no beam failureand/or of a successful BFR procedure. If there is a beam failure and/ora failure of a BFR procedure for a second cell indicated by a cell indexin one of the cell index fields, a wireless device may populate theadditional data field, associated with that cell index field, with avalue (e.g., a different one of the reserved values from FIG. 25 (e.g.,1111111)) indicative of the unsuccessful BFR (and/or of the beamfailure). A base station receiving the beam report 2604 may determine,for each of the one or more second cells associated with cell indexes inthe cell index fields, whether a BFR procedure of that second cell wasunsuccessful and/or whether a beam failure occurred in that second cell.That determination by the base station may be based on whether each ofthe additional data fields associated with the cell index fields iseither (i) empty and/or populated a value indicative of no beam failure(or of successful BFR), or (ii) populated with a value indicative of anunsuccessful BFR (and/or of a beam failure). The base station may, basedon determining an unsuccessful BFR procedure and/or a beam failure forone of the second cells, send a MAC CE to deactivate that second celland/or may refrain from scheduling the wireless device on that secondcell.

In the example of FIG. 26D, a wireless device may indicate that a randomaccess procedure for a BFR procedure for a second cell, indicated in thebeam report 2604 by the cell index “Cell 2,” was unsuccessful bypopulating the additional field, associated with the cell index fieldcontaining the cell index “Cell 2,” with a value (e.g., the reservedvalue 1111111 from FIG. 25) indicating an unsuccessful BFR procedure. Abase station receiving that beam report 2604 may be informed of thefailure of the BFR procedure for the second cell “Cell 2.” The basestation may, based on the failed BFR procedure, send a MAC CE todeactivate, and/or may refrain from scheduling the wireless device on,the second cell “Cell 2.”

A wireless device may receive, for example, from a base station, one ormore messages comprising one or more configuration parameters of a firstcell (e.g., a PCell) and/or of a second cell (e.g., an SCell). The oneor more configuration parameters may indicate at least one of one ormore first RSs of the second cell; one or more second RSs of the secondcell; and/or one or more beam BFRQ resources. The BFRQ resources may,for example, be on the first cell. The BFRQ resources may, for example,be on the second cell. The one or more configuration parameters mayindicate an association between each of the one or more second RSs andeach of the one or more BFRQ resources. The one or more first RSs maycomprise one or more first CSI-RSs and/or one or more first SS blocks.The one or more second RSs may comprise one or more second CSI-RSsand/or one or more second SS blocks.

A wireless device may initiate a random access procedure for a beamfailure recovery for the second cell based on, for example, reaching anumber of beam failure instance indications for the second cell. Thenumber of beam failure instance indications may be configured by ahigher layer (e.g., an RRC layer). The beam failure instance indicationsmay comprise, for example, an indication of a beam failure instance froma physical layer of the wireless device to a medium-access layer of thewireless device. The beam failure instance may comprise assessing theone or more first RSs with radio quality lower than a first threshold.The first threshold may, for example, be based on hypothetical BLER, onRSRP, on RSRQ, and/or on SINR. The wireless device may, based on, forexample, the initiating the random access procedure, start a BFR timer(if configured).

The random access procedure may comprise, for example, selecting aselected RS in the one or more second RSs from the configurationparameters. The selected RS may be associated with a BFRQ resource. TheBFRQ resource may be, for example, one of the one or more BRFQ resourcesfrom the configuration parameters. The BFRQ resource may comprise atleast one preamble and at least one random access channel resource of aBWP. The random access procedure may further comprise sending (e.g.,transmitting), by the wireless device, the at least one preamble via theat least one random access channel resource. The at least one randomaccess channel resource may comprise one or more time resources and/orone or more frequency resources. The selected RS may, for example, beassociated with one of the one or more second RSs with radio qualityhigher than a second threshold. The second threshold may be based onL1-RSRP, on RSRQ, on hypothetical BLER, and/or on SINR.

Based on sending (e.g., transmitting) the at least one preamble in afirst slot, the wireless device may start, from a second slot,monitoring for a BFR response. The monitoring for the BFR response maycomprise monitoring at least one PDCCH in one or more CORESETs for firstDCI (e.g., a downlink assignment or an uplink grant) within a configuredresponse window. The first DCI may be with CRC scrambled by a C-RNTI ofthe wireless device. The one or more CORESETs may, for example, be onthe second cell. The one or more CORESETs may, for example, be on thefirst cell. The random access procedure for the BFR procedure may, forexample, based on receiving the first DCI on the at least one PDCCH inthe one or more CORESETs, within the configured response window, besuccessfully completed.

A BFR procedure may be unsuccessfully completed if, for example, amaximum number of transmissions of the at least one preamble via theBFRQ resource for the BFR procedure is reached without the BFR procedurebeing successfully completed. The maximum number of the transmissions(e.g., a maximum number of preamble transmissions) may be configured bya higher layer. A BFR procedure may be unsuccessfully completed if, forexample, a BFR timer (if configured) expires before the BFR procedure issuccessfully completed (e.g., if the BFR timer expires before thewireless device receives, based on sending the at least one preamble,DCI within a configured response window).

A wireless device may send (e.g., transmit), based on a failure of a BFRprocedure for an SCell, a beam report, The wireless device may send thebeam report, for example, via an uplink control channel of the firstcell. The beam report may comprise, for example, one or more fieldsindicating that the random access procedure for the beam failurerecovery is unsuccessful. The beam report may be sent (e.g.,transmitted) via a radio resource of periodic beam report resources of aPUCCH. The one or more fields may, for example, comprise one or morebeam index fields and one or more associated measurement/data fields Theone or more associated measurement/data fields may, for example, be usedto indicate that the random access procedure for the beam failurerecovery is unsuccessful by including, in one or more of themeasurement/data fields (e.g., as described in connection with FIGS.26A-26D), a value (e.g., a reserved value of FIG. 25) indicatingunsuccessful beam failure recovery.

PUCCH beam reporting to indicate an unsuccessful BFR procedure and/or abeam failure, for example, as described in connection with FIGS.26A-26C, may be used with CQI reporting. A wireless device may, forexample, use a first CQI reporting of a second cell. The first CQIreporting may comprise one or more beam index fields and one or moremeasurement fields. One or more beam indexes indicated in the one ormore beam index fields may be associated (e.g., QCLed) with one or moreRSs of the second cell. Also or alternatively, one or more of the one ormore beam index fields may not be associated with an RS and may bededicated to and/or otherwise used for indicating an unsuccessful BFRprocedure. Each of the one or more measurement fields may comprise avalue that indicates a value or range of values (e.g., an L1-RSRP valueor range of values) of one of the one or more beam indexes.

If the second cell has an unsuccessful BFR procedure, the wirelessdevice may indicate the unsuccessful BFR procedure for the second cellby setting one or more of the one or more measurement fields in the CQIreporting to a value (e.g., reserved value (e.g., 0)) indicatingunsuccessful BFR. A base station that receives the CQI reporting withone or more of the one or more measurement fields set to the valueindicating unsuccessful BFR may be made aware of the failure of the BFRprocedure of the second cell. The base station may, for example, basedon the unsuccessful BFR, send a MAC CE to deactivate the second celland/or may refrain from scheduling the wireless device on the secondcell.

Using, for example, a report similar to that described in connectionwith FIG. 26D, a wireless device may send a second CQI reporting of afirst cell (e.g., a PCell) to notify a base station of a failure of aBFR procedure for one or more serving second cells (e.g., SCells) otherthan the first cell. The second CQI reporting of the first cell maycomprise, for the first cell, values (e.g., non-reserved values)indicating values or ranges of values for a characteristic. The secondCQI reporting of the first cell may comprise an indication of a failureof random access procedure for a BFR of one or more of the second cells.The second CQI reporting of the first cell may comprise one or moreadditional cell index fields, comprising one or more additional cellindexes of the one or more second cells (e.g., the indexes “Cell 1” to“Cell K” shown in FIG. 26D), and one or more additional data fields.Each of the one or more additional cell indexes may be associated withone of the one or more second cells and with a value (or absence of avalue) in one of the one or more additional data fields. If there is nobeam failure or unsuccessful BFR procedure for one of the second cells,the associated additional data field may be empty or may comprise avalue (e.g., a second reserved value) indicative of no beam failureand/or of no unsuccessful BFR procedure. If there is an unsuccessful BFRprocedure (and/or beam failure) for one of the second cells, theassociated additional data field may comprise a value (e.g., a firstreserved value) indicative of beam failure and/or of an unsuccessful BFRprocedure). A base station the receives the second CQI reporting of thefirst cell may determine, for each of the one or more second cells,whether a BFR procedure of that second cell was unsuccessful and/orwhether a beam failure occurred in that second cell.

Other types of reporting may be used to report failure of a BFRprocedure for an SCell. Periodic CSI reporting, for example, may be usedto report an unsuccessful BFR procedure for an SCell. CSI reporting maybe used, for example, similar to the use of beam reporting described inconnection with FIGS. 26A-26B, to include an indicator (e.g., a reservedn-bit value from a set of n-bit values that includes indicators ofmeasurements for one or more signal characteristics) of an unsuccessfulBFR procedure for an SCell. The indicator of the unsuccessful BFRprocedure may replace an indicator of a measurement, and/or may beincluded in addition to one or more indicators of the measurement.

An RLF report may, for example, comprise a serving cell index. Each ofone or more serving cells of a wireless device may be configured with aserving cell index. The wireless device may, for example, if thewireless device has a failure of a BFR procedure for a serving cell,include the serving cell index of that serving cell in the RLF report. Abase station, based on receiving the RLF report, may be made aware ofthe failure of the BFR procedure for the serving cell. The base stationmay, based on that failure of the BFR procedure, send a MAC CE todeactivate the serving cell and/or may refrain from scheduling thewireless device on the serving cell.

A base station may, for example, request an RLF report (e.g.,periodically). An indication of a failure of a BFR procedure of aserving cell may be stored in an RLF report. The RLF report may containa serving cell index of that serving cell. A wireless device informationrequest procedure (e.g., an RRC UE information request procedure) may bereused to carry, to the network, that RLF report storing the indicationof the failure of a BFR procedure.

One or more portions of one or more of the example reports describedabove, and/or one or more of the example procedures described above, mayalso or alternatively be used for other types of beam-relatedprocedures. Reports (e.g., reports similar to those described inconnection FIGS. 26B through 26D) may, for example, be used to reportBFR procedures that have not yet completed and/or have not yet failed,to report BFR procedures that have successfully completed, and/or forother reporting.

A method may comprise receiving, by a wireless device, configurationparameters that indicate at least one reference signal (RS). The methodmay comprise initiating a beam failure recovery (BFR) procedure for asecondary cell. The method may comprise determining that the BFRprocedure is unsuccessful. The method may comprise sending, via aphysical uplink control channel (PUCCH), at least one message. The atleast one message may comprise at least one field associated with the atleast one RS. The at least one message may comprise at least oneindicator of the unsuccessful BFR procedure. The at least one field maycomprise at least one indicator of a value of a layer-1 reference signalreceived power (L1-RSRP) of the at least one RS. The at least one fieldmay comprise the at least one indicator of the unsuccessful BFRprocedure. The PUCCH may be associated with another secondary celldifferent from the secondary cell. The PUCCH may be associated with aprimary cell. The method may comprise stopping, by the wireless deviceand based on the unsuccessful BFR procedure, monitoring of at least onedownlink physical channel associated with the secondary cell. The methodmay comprise stopping, by the wireless device and based on theunsuccessful BFR procedure, uplink transmissions via the secondary cell.The configuration parameters may indicate a cell deactivation timerassociated with the secondary cell. The stopping may comprise stopping,before expiration of the cell deactivation timer, the uplinktransmissions via the secondary cell. The determining that the BFRprocedure is unsuccessful may be based on at least one of: an expirationof a BFR timer associated with the secondary cell, or sending of amaximum quantity of uplink signals for the BFR procedure. The at leastone RS may comprise a plurality of RSs, and the at least one field maycomprise a plurality of fields associated with the plurality of RSs. Theat least one RS may be associated with the secondary cell. The at leastone RS may be associated with a primary cell. The at least one field maycomprise an m-bit value selected from a plurality of m-bit values. Afirst portion of the plurality of m-bit values may be mapped to signalmeasurement values. A second portion of the plurality of m-bit valuesmay optionally not be mapped to signal measurement values.

A method may comprise receiving, by a wireless device, configurationparameters that indicate at least one field associated with ameasurement value associated with at least a first downlink signal. Themethod may comprise initiating a beam failure recovery (BFR) procedurefor a secondary cell. The method may comprise determining that the BFRprocedure is unsuccessful. The method may comprise sending, via aphysical uplink control channel (PUCCH), at least one messagecomprising, in the at least one field, at least one indicator of theunsuccessful BFR procedure. The at least one message may comprise, for asecond downlink signal, an indicator of a measurement value associatedwith the second downlink signal. The PUCCH may be associated with aprimary cell. The method may comprise stopping, by the wireless deviceand based on the unsuccessful BFR procedure, uplink transmissions viathe secondary cell.

A method may comprise initiating, by a wireless device, a beam failurerecovery (BFR) procedure for a secondary cell. The method may comprisedetermining that the BFR procedure is unsuccessful. The method maycomprise discontinuing, by the wireless device, based on theunsuccessful BFR procedure, and before expiration of a secondary celldeactivation timer associated with the secondary cell, at least one of:monitoring at least one downlink physical channel associated with thesecondary cell, or uplink transmissions via the secondary cell. Themethod may comprise sending, via a physical uplink control channel(PUCCH), at least one message. The at least one message may comprise atleast one indicator of the unsuccessful BFR procedure. The at least onemessage may comprise at least one indicator of a measurement valueassociated with at least one reference signal (RS). The method maycomprise receiving, by the wireless device, one or more messagescomprising configuration parameters that indicate the at least one RS.The at least one indicator of the measurement value may comprise atleast one indicator of a value of a layer-1 reference signal receivedpower (L1-RSRP) of the at least one RS.

A method may comprise receiving, by a wireless device, one or moremessages comprising configuration parameters of a secondary cell,wherein the configuration parameters indicate one or more RSs of thesecondary cell; initiating a BFR procedure for the secondary cell inresponse to reaching a number of beam failure instance indications forthe secondary cell; determining that the BFR procedure is unsuccessfullycompleted; setting one or more fields, in a report for measurementvalues of the one or more RSs, to a reserved value based on thedetermining; and transmitting the report via a physical uplink controlchannel. Each of the one or more fields may correspond to a respectiveone of the one or more RSs. The report may comprise a cell index foreach of the one or more fields. The physical uplink control channel maybe a physical uplink control channel of the secondary cell. The physicaluplink control channel may be a physical uplink control channel of aprimary cell. The configuration parameters may further indicate a beamfailure recovery timer. The determining that the BFR procedure isunsuccessfully completed may comprise expiring of the beam failurerecovery timer. The configuration parameters further indicate a maximumnumber of uplink transmissions. The initiating the BFR procedure maycomprise transmitting an uplink signal via an uplink resource. Themethod may comprise incrementing a transmission number based on thetransmitting the uplink signal. The determining that the BFR procedureis unsuccessfully completed may comprise the transmission numberreaching a maximum number of uplink transmissions. The method maycomprise stopping one or more uplink transmissions via the secondarycell based on the determining that the BFR procedure is unsuccessfullycompleted. The method may comprise stopping monitoring at least onephysical downlink control channel in a CORESET based on the determiningthat the BFR procedure is unsuccessfully completed. The CORESET may beconfigured for the secondary cell. The CORESET may be configured for aprimary cell. The method may comprise transmitting an RLF reportcomprising the cell index. The method may comprise resuming the one ormore uplink transmissions based on determining that a radio quality ofat least one physical downlink control channel in the CORESET is higherthan a threshold. The initiating the BFR procedure may compriseassessing one or more second RSs with radio quality lower than a secondthreshold. The configuration parameters may indicate the one or moresecond RSs for the secondary cell. The configuration parameters furtherindicate the second threshold. A method may comprise receiving, by awireless device, one or more messages comprising one or moreconfiguration parameters of a secondary cell; initiating a beam failurerecovery procedure for the secondary cell in response to reaching anumber of beam failure instance indications for the secondary cell;unsuccessfully completing the beam failure recovery procedure; andtransmitting a beam report, via a physical uplink control channel,comprising a reserved value indicating that the beam failure recoveryprocedure has unsuccessfully completed.

FIG. 27 shows example elements of a computing device that may be used toimplement any of the various devices described herein, including, e.g.,the base station 120A and/or 120B, the wireless device 110 (e.g., 110Aand/or 110B), or any other base station, wireless device, or computingdevice described herein. The computing device 2700 may include one ormore processors 2701, which may execute instructions stored in therandom access memory (RAM) 2703, the removable media 2704 (such as aUniversal Serial Bus (USB) drive, compact disk (CD) or digital versatiledisk (DVD), or floppy disk drive), or any other desired storage medium.Instructions may also be stored in an attached (or internal) hard drive2705. The computing device 2700 may also include a security processor(not shown), which may execute instructions of one or more computerprograms to monitor the processes executing on the processor 2701 andany process that requests access to any hardware and/or softwarecomponents of the computing device 2700 (e.g., ROM 2702, RAM 2703, theremovable media 2704, the hard drive 2705, the device controller 2707, anetwork interface 2709, a GPS 2711, a Bluetooth interface 2712, a WiFiinterface 2713, etc.). The computing device 2700 may include one or moreoutput devices, such as the display 2706 (e.g., a screen, a displaydevice, a monitor, a television, etc.), and may include one or moreoutput device controllers 2707, such as a video processor. There mayalso be one or more user input devices 2708, such as a remote control,keyboard, mouse, touch screen, microphone, etc. The computing device2700 may also include one or more network interfaces, such as a networkinterface 2709, which may be a wired interface, a wireless interface, ora combination of the two. The network interface 2709 may provide aninterface for the computing device 2700 to communicate with a network2710 (e.g., a RAN, or any other network). The network interface 2709 mayinclude a modem (e.g., a cable modem), and the external network 2710 mayinclude communication links, an external network, an in-home network, aprovider's wireless, coaxial, fiber, or hybrid fiber/coaxialdistribution system (e.g., a DOCSIS network), or any other desirednetwork. Additionally, the computing device 2700 may include alocation-detecting device, such as a global positioning system (GPS)microprocessor 2711, which may be configured to receive and processglobal positioning signals and determine, with possible assistance froman external server and antenna, a geographic position of the computingdevice 2700.

The example in FIG. 27 may be a hardware configuration, although thecomponents shown may be implemented as software as well. Modificationsmay be made to add, remove, combine, divide, etc. components of thecomputing device 2700 as desired. Additionally, the components may beimplemented using basic computing devices and components, and the samecomponents (e.g., processor 2701, ROM storage 2702, display 2706, etc.)may be used to implement any of the other computing devices andcomponents described herein. For example, the various componentsdescribed herein may be implemented using computing devices havingcomponents such as a processor executing computer-executableinstructions stored on a computer-readable medium, as shown in FIG. 27.Some or all of the entities described herein may be software based, andmay co-exist in a common physical platform (e.g., a requesting entitymay be a separate software process and program from a dependent entity,both of which may be executed as software on a common computing device).

The disclosed mechanisms herein may be performed if certain criteria aremet, for example, in a wireless device, a base station, a radioenvironment, a network, a combination of the above, and/or the like.Example criteria may be based on, for example, wireless device and/ornetwork node configurations, traffic load, initial system set up, packetsizes, traffic characteristics, a combination of the above, and/or thelike. If the one or more criteria are met, various examples may be used.It may be possible to implement examples that selectively implementdisclosed protocols.

A base station may communicate with a mix of wireless devices. Wirelessdevices and/or base stations may support multiple technologies, and/ormultiple releases of the same technology. Wireless devices may have somespecific capability(ies) depending on wireless device category and/orcapability(ies). A base station may comprise multiple sectors. A basestation communicating with a plurality of wireless devices may refer tobase station communicating with a subset of the total wireless devicesin a coverage area. Wireless devices referred to herein may correspondto a plurality of wireless devices of a particular LTE or 5G releasewith a given capability and in a given sector of a base station. Aplurality of wireless devices may refer to a selected plurality ofwireless devices, and/or a subset of total wireless devices in acoverage area. Such devices may operate, function, and/or perform basedon or according to drawings and/or descriptions herein, and/or the like.There may be a plurality of base stations or a plurality of wirelessdevices in a coverage area that may not comply with the disclosedmethods, for example, because those wireless devices and/or basestations perform based on older releases of LTE or 5G technology.

One or more features described herein may be implemented in acomputer-usable data and/or computer-executable instructions, such as inone or more program modules, executed by one or more computers or otherdevices. Generally, program modules include routines, programs, objects,components, data structures, etc. that perform particular tasks orimplement particular abstract data types when executed by a processor ina computer or other data processing device. The computer executableinstructions may be stored on one or more computer readable media suchas a hard disk, optical disk, removable storage media, solid statememory, RAM, etc. The functionality of the program modules may becombined or distributed as desired. The functionality may be implementedin whole or in part in firmware or hardware equivalents such asintegrated circuits, field programmable gate arrays (FPGA), and thelike. Particular data structures may be used to more effectivelyimplement one or more features described herein, and such datastructures are contemplated within the scope of computer executableinstructions and computer-usable data described herein.

Many of the elements in examples may be implemented as modules. A modulemay be an isolatable element that performs a defined function and has adefined interface to other elements. The modules may be implemented inhardware, software in combination with hardware, firmware, wetware(i.e., hardware with a biological element) or a combination thereof, allof which may be behaviorally equivalent. For example, modules may beimplemented as a software routine written in a computer languageconfigured to be executed by a hardware machine (such as C, C++,Fortran, Java, Basic, Matlab or the like) or a modeling/simulationprogram such as Simulink, Stateflow, GNU Octave, or LabVIEWMathScript.Additionally or alternatively, it may be possible to implement modulesusing physical hardware that incorporates discrete or programmableanalog, digital and/or quantum hardware. Examples of programmablehardware may comprise: computers, microcontrollers, microprocessors,application-specific integrated circuits (ASICs); field programmablegate arrays (FPGAs); and complex programmable logic devices (CPLDs).Computers, microcontrollers, and microprocessors may be programmed usinglanguages such as assembly, C, C++ or the like. FPGAs, ASICs, and CPLDsmay be programmed using hardware description languages (HDL), such asVHSIC hardware description language (VHDL) or Verilog, which mayconfigure connections between internal hardware modules with lesserfunctionality on a programmable device. The above-mentioned technologiesmay be used in combination to achieve the result of a functional module.

A non-transitory tangible computer readable media may compriseinstructions executable by one or more processors configured to causeoperations of multi-carrier communications described herein. An articleof manufacture may comprise a non-transitory tangible computer readablemachine-accessible medium having instructions encoded thereon forenabling programmable hardware to cause a device (e.g., a wirelessdevice, wireless communicator, a wireless device, a base station, andthe like) to allow operation of multi-carrier communications describedherein. The device, or one or more devices such as in a system, mayinclude one or more processors, memory, interfaces, and/or the like.Other examples may comprise communication networks comprising devicessuch as base stations, wireless devices or user equipment (wirelessdevice), servers, switches, antennas, and/or the like. A network maycomprise any wireless technology, including but not limited to,cellular, wireless, WiFi, 4G, 5G, any generation of 3GPP or othercellular standard or recommendation, wireless local area networks,wireless personal area networks, wireless ad hoc networks, wirelessmetropolitan area networks, wireless wide area networks, global areanetworks, space networks, and any other network using wirelesscommunications. Any device (e.g., a wireless device, a base station, orany other device) or combination of devices may be used to perform anycombination of one or more of steps described herein, including, forexample, any complementary step or steps of one or more of the abovesteps.

Although examples are described above, features and/or steps of thoseexamples may be combined, divided, omitted, rearranged, revised, and/oraugmented in any desired manner. Various alterations, modifications, andimprovements will readily occur to those skilled in the art. Suchalterations, modifications, and improvements are intended to be part ofthis description, though not expressly stated herein, and are intendedto be within the spirit and scope of the descriptions herein.Accordingly, the foregoing description is by way of example only, and isnot limiting.

1. A method comprising: determining, by a wireless device, that a beamfailure recovery (BFR) procedure, for a beam failure associated with acell, is unsuccessful; and sending, via a physical uplink controlchannel (PUCCH), at least one message comprising at least onemeasurement field associated with at least one reference signal (RS),wherein the at least one measurement field comprises a first value thatindicates the unsuccessful BFR procedure associated with the cell. 2.The method of claim 1, wherein the at least one measurement fieldfurther comprises at least one indicator of a value of an RS receivedpower (RSRP) of the at least one RS.
 3. The method of claim 1, whereinthe at least one message further comprises at least one field comprisinga value indicating the at least one RS.
 4. The method of claim 1,wherein the PUCCH is associated with at least one of: a primary cell; ora secondary cell different from the cell.
 5. The method of claim 1,further comprising stopping, based on the unsuccessful BFR procedure, atleast one of: uplink transmissions via the cell; or monitoring of atleast one downlink channel associated with the cell.
 6. The method ofclaim 1, further comprising: receiving at least one configurationparameter indicating a cell deactivation timer associated with the cell;and stopping, before expiration of the cell deactivation timer and basedon the unsuccessful BFR procedure, at least one of: uplink transmissionsvia the cell; or monitoring of at least one downlink channel associatedwith the cell.
 7. The method of claim 1, wherein the determining thatthe BFR procedure is unsuccessful is based on at least one of: anexpiration of a BFR timer associated with the cell; or sending of amaximum quantity of uplink signals for the BFR procedure.
 8. The methodof claim 1, wherein the at least one RS comprises a plurality of RSs,and wherein at least one field, of the at least one message, comprises aplurality of fields associated with the plurality of RSs.
 9. The methodof claim 1, wherein the at least one RS comprises at least one of: an RSof a primary cell; an RS of a secondary cell; or an RS of the cell. 10.The method of claim 1, further comprising: receiving at least oneconfiguration parameter that indicates the at least one RS; anddetermining a beam failure associated with the cell.
 11. The method ofclaim 1, wherein the first value corresponds to a reserved value of aplurality of layer-1 RS received power (L1-RSRP) values, and wherein asecond value, different from the reserved value, for the at least onemeasurement field of the at least one message is configured to indicatea measured L1-RSRP.
 12. The method of claim 1, further comprisingmeasuring the at least one RS for measurement reporting, wherein the atleast one measurement field is configured to indicate a measuredcharacteristic of the at least one RS.
 13. The method of claim 1,wherein the first value corresponds to a reserved value associated withan RS received power, and wherein the at least one message furthercomprises a second value, different from the reserved value, forindicating an RS received power associated with another cell differentfrom the cell.
 14. A wireless device comprising: one or more processors;and memory storing instructions that, when executed by the one or moreprocessors, cause the wireless device to: determine that a beam failurerecovery (BFR) procedure, for a beam failure associated with a cell, isunsuccessful; and send, via a physical uplink control channel (PUCCH),at least one message comprising at least one measurement fieldassociated with at least one reference signal (RS), wherein the at leastone measurement field comprises a first value that indicates theunsuccessful BFR procedure associated with the cell.
 15. The wirelessdevice of claim 14, wherein the at least one measurement field furthercomprises at least one indicator of a value of an RS received power(RSRP) of the at least one RS.
 16. The wireless device of claim 14,wherein the at least one message further comprises at least one fieldcomprising a value indicating the at least one RS.
 17. The wirelessdevice of claim 14, wherein the PUCCH is associated with at least oneof: a primary cell; or a secondary cell different from the cell.
 18. Thewireless device of claim 14, wherein the instructions, when executed bythe one or more processors, cause the wireless device to stop, based onthe unsuccessful BFR procedure, at least one of: uplink transmissionsvia the cell; or monitoring of least one downlink channel associatedwith the cell.
 19. The wireless device of claim 14, wherein theinstructions, when executed by the one or more processors, cause thewireless device to: receive at least one configuration parameterindicating a cell deactivation timer associated with the cell; and stop,before expiration of the cell deactivation timer and based on theunsuccessful BFR procedure, at least one of: uplink transmissions viathe cell; or monitoring of at least one downlink channel associated withthe cell.
 20. The wireless device of claim 14, wherein the instructions,when executed by the one or more processors, cause the wireless deviceto determine that the BFR procedure is unsuccessful based on at leastone of: an expiration of a BFR timer associated with the cell; orsending of a maximum quantity of uplink signals for the BFR procedure.21. The wireless device of claim 14, wherein the at least one RScomprises a plurality of RSs, and wherein at least one field, of the atleast one message, comprises a plurality of fields associated with theplurality of RSs.
 22. The wireless device of claim 14, wherein the atleast one RS comprises at least one of: an RS of a primary cell; an RSof a secondary cell; or an RS of the cell.
 23. The wireless device ofclaim 14, wherein the instructions, when executed by the one or moreprocessors, cause the wireless device to: receive at least oneconfiguration parameter that indicates the at least one RS; anddetermine a beam failure associated with the cell.
 24. The wirelessdevice of claim 14, wherein the first value corresponds to a reservedvalue of a plurality of layer-1 RS received power (L1-RSRP) values, andwherein a second value, different from the reserved value, for the atleast one measurement field of the at least one message is configured toindicate a measured L1-RSRP.
 25. The wireless device of claim 14,wherein the instructions, when executed by the one or more processors,cause the wireless device to measure the at least one RS for measurementreporting, and wherein the at least one measurement field is configuredto indicate a measured characteristic of the at least one RS.
 26. Thewireless device of claim 14, wherein the first value corresponds to areserved value associated with an RS received power, and wherein the atleast one message further comprises a second value, different from thereserved value, for indicating an RS received power associated withanother cell different from the cell.
 27. A computer-readable mediumstoring instructions that, when executed, configure a wireless deviceto: determine that a beam failure recovery (BFR) procedure, for a beamfailure associated with a cell, is unsuccessful; and send, via aphysical uplink control channel (PUCCH), at least one message comprisingat least one measurement field associated with at least one referencesignal (RS), wherein the at least one measurement field comprises afirst value that indicates the unsuccessful BFR procedure associatedwith the cell.
 28. The computer-readable medium of claim 27, wherein theat least one measurement field further comprises at least one indicatorof a value of an RS received power (RSRP) of the at least one RS. 29.The computer-readable medium of claim 27, wherein the at least onemessage further comprises at least one field comprising a valueindicating the at least one RS.
 30. The computer-readable medium ofclaim 27, wherein the PUCCH is associated with at least one of: aprimary cell; or a secondary cell different from the cell.
 31. Thecomputer-readable medium of claim 27, wherein the instructions, whenexecuted, further configure the wireless device to stop, based on theunsuccessful BFR procedure, at least one of: uplink transmissions viathe cell; or monitoring of least one downlink channel associated withthe cell.
 32. The computer-readable medium of claim 27, wherein theinstructions, when executed, further configure the wireless device to:receive at least one configuration parameter indicating a celldeactivation timer associated with the cell; and stop, before expirationof the cell deactivation timer and based on the unsuccessful BFRprocedure, at least one of: uplink transmissions via the cell; ormonitoring of at least one downlink channel associated with the cell.33. The computer-readable medium of claim 27, wherein the instructions,when executed, further configure the wireless device to determine thatthe BFR procedure is unsuccessful based on at least one of: anexpiration of a BFR timer associated with the cell; or sending of amaximum quantity of uplink signals for the BFR procedure.
 34. Thecomputer-readable medium of claim 27, wherein the at least one RScomprises a plurality of RSs, and wherein at least one field, of the atleast one message, comprises a plurality of fields associated with theplurality of RSs.
 35. The computer-readable medium of claim 27, whereinthe at least one RS comprises at least one of: an RS of a primary cell;an RS of a secondary cell; or an RS of the cell.
 36. Thecomputer-readable medium of claim 27, wherein the instructions, whenexecuted, further configure the wireless device to: receive at least oneconfiguration parameter that indicates the at least one RS; anddetermine a beam failure associated with the cell.
 37. Thecomputer-readable medium of claim 27, wherein the first valuecorresponds to a reserved value of a plurality of layer-1 RS receivedpower (L1-RSRP) values, and wherein a second value, different from thereserved value, for the at least one measurement field of the at leastone message is configured to indicate a measured L1-RSRP.
 38. Thecomputer-readable medium of claim 27, wherein the instructions, whenexecuted, further configure the wireless device to measure the at leastone RS for measurement reporting, and wherein the at least onemeasurement field is configured to indicate a measured characteristic ofthe at least one RS.
 39. The computer-readable medium of claim 27,wherein the first value corresponds to a reserved value associated withan RS received power, and wherein the at least one message furthercomprises a second value, different from the reserved value, forindicating an RS received power associated with another cell differentfrom the cell.